Create file /etc/systemd/system/docker-compose@.service
[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.service| /* optional */ | |
| * { margin: 0; padding: 0; border: 0 none; font-size: 100%; } | |
| body { padding: 10em; background: #FFF; color: #333; font: 14px/1.5 sans-serif; } | |
| /* unordered lists */ | |
| ul { | |
| margin: 0 0 1.5em; | |
| padding: 0; | |
| list-style: none; | |
| } |
| C:\Program Files (x86)\MSBuild\12.0\Bin\Microsoft.Common.CurrentVersion.targets | |
| <Target Name="_CheckForInvalidConfigurationAndPlatform"></Target> | |
| <Target Name="Build" Condition=" '$(_InvalidConfigurationWarning)' != 'true' " DependsOnTargets="$(BuildDependsOn)" Returns="$(TargetPath)" /> | |
| <Target Name="BeforeBuild" /> | |
| <Target Name="AfterBuild" /> | |
| <Target Name="CoreBuild" DependsOnTargets="$(CoreBuildDependsOn)"></Target> | |
| <Target Name="Rebuild" Condition=" '$(_InvalidConfigurationWarning)' != 'true' " DependsOnTargets="$(RebuildDependsOn)" Returns="$(TargetPath)" /> | |
| <Target Name="BeforeRebuild" /> | |
| <Target Name="AfterRebuild" /> | |
| <Target Name="BuildGenerateSources" DependsOnTargets="BuildGenerateSourcesTraverse;$(BuildGenerateSourcesAction)" /> |
| # Put this file to /etc/rsyslog.d as 99-logstash.con | |
| # | |
| # Make spool directory -p /var/spool/rsyslog when needed | |
| # | |
| # Change last address | |
| # $WorkDirectory /var/spool/rsyslog # use this if you don't like default /var/lib/rsyslog | |
| $ActionQueueFileName logstash # unique name prefix for spool files | |
| $ActionQueueMaxDiskSpace 1g # 1gb limit on log queue |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Box Shadow</title> | |
| <style> | |
| .box { | |
| height: 150px; | |
| width: 300px; | |
| margin: 20px; |
Here is some opinionated guidance maybe to save some part of your valuable lifetime. The following topics focus on: development, architecture and maintainability.
The primary advice after John Skeet: Just solve your issue in the simplest possible way. Limit the boundaries: what are the requirements? Don't try to solve meta-level problems of every software engineer ever. Draft the boundaries even if you're writing a general library: Users can compose multiple small libraries if necessary. Expect your requirement specifications, if any, could be better, that's life.