CSW (Catalogue Service for the Web) is an `OGC (Open Geospatial Consortium)`_ specification that defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources.
[Unit] | |
Description=Mount /proc/xen files | |
ConditionPathExists=/proc/xen | |
RefuseManualStop=true | |
[Mount] | |
What=xenfs | |
Where=/proc/xen | |
Type=xenfs |
Based on copy of https://gist.github.com/kalxas/5ab6237b4163b0fdc930 on 20 June 2014 12:27 UTC |
#!/bin/bash | |
# gem install ghi (https://github.com/stephencelis/ghi) | |
set -o errexit | |
set -o pipefail | |
skills=(angular build-infrastructure campaign-finance copy design html-css jekyll js ruby sysadmin) | |
skill_color="#fef2c0" | |
features=(candidate committee contributions data historic-election multi-city page referendum search usability) |
At the end of 2016, the [CALC][] team experimented with converting the single-page app on its front page, referred to as the [Data Explorer][], from JQuery to React + Redux.
We inherited the [1350-line explorer.js
][explorer-1] from a previous
team. This code was written under different project and time constraints,
Moved to https://github.com/18F/ghadmin.
- Official handbook page
- Save the usernames and passwords for systems you may need when you are no longer an employee, such as
- Employee Express
- Benefeds (dental and vision insurance)
- The website for your medical insurance
- FSAFEDS
- TSP
- Log into Employee Express
- Write down your login information for employee express. You can't get this back after you leave GSA.
- Switch your W2s to Mail instead of Electronic
There are a number of different strategies for enabling API authentication for system-to-system authentication between two parties. All of them have some advantages and disadvantages.
The simplest approach is typically to pass a secret API key as a header or using HTTP basic auth. The client provides a secret value in the Authorization
or Bearer
header. The server matches the key against a stored value for that account. This relies on the security of HTTPS / TLS to provide confidentiality and integrity. This approach excels for websites with a lot of end-users who need to be able to manage their own keys through a web interface or API. It's so simple that clients don't need any custom code.
- Very simple to implement for both clients and servers