SystemAdministration-OLD-2024: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
==Resources== | ==Resources== | ||
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turn off | * [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turn off | ||
* [[ | * [[EmergencyTechnicalProcedures]] - in case of fire, break glass (Read before messing with servers) | ||
[[Category:Teams]] | [[Category:Teams]] | ||
[[Category:System administration]] | [[Category:System administration]] | ||
Revision as of 23:00, 15 March 2014
TeamPages - parent, Development
Welcome
Who we are
- robinld -- systems
- mechanicjay -- systems
Index of Development Pages and Resources
Servers
- soylent-www - Primary Apache and slash server for main site.
- soylent-db -- mysql server, holds the slash database
- slashcott - Holds the slashcott site, development machine
- soylent-services - mail, wiki, other services as needed
Known Problems
- There are errors in the zone file in the spf TXT record -- Mechanicjay would be happy to fix this and clean up the zone file in general, but needs linode manager access from NCommander.
- No init script for Apache.
- Broken https configuration
- Nginx running
Work Notes
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file soylent-services with bind and having external services handle serving out our dns.
Resources
- DnsRecords - copy of the zone file pasted from the machine that was accidentally turn off
- EmergencyTechnicalProcedures - in case of fire, break glass (Read before messing with servers)