| <script> | |
| window.statuspalWidget = { | |
| subdomain: 'meta', | |
| selector: '.sp-status', // Optional | |
| position: 'top', // Optional [top | bottom | left | right] - defaults to top. | |
| // Customise copy below | |
| copy: { | |
| status: { | |
| ok: 'All systems operational 1', | |
| scheduled: 'Ongoing scheduled maintenance', |
| .metrics .metric .metric--chart-container, .metrics .metric .metric--chart-container svg { | |
| background: transparent !important; | |
| } | |
| .metrics .metric .metric--chart-container svg .bg { | |
| fill: transparent !important; | |
| } | |
| svg text { | |
| fill: #9cb3c9 !important; | |
| } | |
| svg .gridlayer, svg .zerolinelayer { |
Use this HTML files to customize your Statuspal status page email template in order to include a company logo, add your business address or otherwise to modify the looks to suit your branding.
In order to configure your company logo just replace the image under the .header class.
| document.addEventListener("DOMContentLoaded", function() { | |
| var $ = document.querySelector.bind(document); | |
| var subButton = $('.subscribe'); | |
| var input = $('[name="subscription[filter]"][value="services"]'); | |
| subButton.addEventListener('click', function () { | |
| setTimeout(function () { | |
| input.checked = true; | |
| input.dispatchEvent(new Event('change')); | |
| }, 0); | |
| }); |
| subscribe_to_updates_1: Subscribe | |
| subscribe_to_updates_2: to Updates | |
| subscribe_to_updates_confirmation: You have been subscribed! | |
| overall_status: | |
| operational: All Systems Operational | |
| issue_singular: There is an ongoing Incident | |
| issue_plural: There are ongoing Incidents | |
| maintenance_singular: There is an ongoing Maintenance | |
| maintenance_plural: There are ongoing Maintenances | |
| about: This is {{name}}'s status page, here you'll find the current status and incident history of {{name}} |
| { | |
| "name": "react-hot-loader-test", | |
| "version": "1.0.0", | |
| "scripts": { | |
| "dev:frontend": "webpack-dev-server --hot", | |
| "server": "node server/server.js", | |
| "dev": "concurrently --kill-others \"npm run dev:frontend\" \"npm run server\"", | |
| }, | |
| "dependencies": { | |
| "express": "^4.15.2" |
| const express = require('express'); | |
| const url = require('url'); | |
| const path = require('path'); | |
| const app = express(); | |
| if (process.env.NODE_ENV !== 'production') { | |
| app.use('/assets', require('proxy-middleware')(url.parse('http://localhost:8080/assets'))); | |
| } else { | |
| app.use('/assets', express.static(path.resolve(__dirname, '../www/assets'))); |
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
