| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing AWS backend uses system containers backed on to the AWS
hosted NFS service (EFS). This has some advantages, but also some
disadvantages.
Using the EFS service allows building a container on one instance,
with the state being held on the EFS, and then launching a new
instance to run the container. Using EFS also provides persistence, at
least beyond individual EC2 instances.
However, build performance when using EFS is poor compared with a
local store without the overhead of the network latency. Additionally,
the startup speed of the container running off EFS is slow compared to
local storage.
This backend doesn't use EFS, instead the Guix store sits on instance
storage. Rather than using a system container for a Mini Environment,
an Amazon Machine Image (AMI) is built instead. The fast local storage
makes builds faster, and using EBS storage for the Mini Envirnoments
as well as not having the overhead of starting Ubuntu, then starting
the container also makes startup faster.
|
|
|
|
| |
This looks to be unnecessary, and the gem is no longer present.
|
|
|
|
|
| |
This will enable garbage collection of the Guix store, without
removing things that are still in use.
|
|
|
|
|
| |
To make accessing classes and modules in lib work in the production
environment.
|
| |
|
|
|
|
|
| |
There is a problem with starting the app in the Rails production
environment, moving the require seems to fix the issue.
|
| |
|
|
|
|
|
| |
As it's not required or useful currently if Guix isn't available
locally.
|
|
|
|
|
| |
To prevent them conflicting. Terraform itself has a locking mechanism,
which isn't being used, but this should be sufficient.
|
|
|
|
| |
And link to this from the mini environment page.
|
| |
|
| |
|
|
|
|
| |
For easier debugging.
|
| |
|
|
|
|
|
|
|
|
| |
Add an index route, and a route to access a historical Terraform state
by index.
This also makes the ordering explicit, and fixes an issue with wrapped
parameters.
|
| |
|
| |
|
|
|
|
|
| |
This is recommended by the Que library, but may come in useful
elsewhere for PostgreSQL specific stuff.
|
|
|
|
|
| |
To allow supporting tracking related TerraformStates for backends as
well.
|
|
|
|
|
|
|
|
|
| |
Change the module to a class, which is used to represent a terraform
working directory.
Change the routing for the terraform http backends, to remove any
connection with mini environments, and remove this concern from the
new TerraformWorkingDirectory class also.
|
|
|
|
| |
Raise everywhere, instead of log, as this is more explicit.
|
|
|
|
|
|
| |
Use gem rather than require in config/boot.rb. This is better, as it
only sets up the $LOAD_PATH, and doesn't actually require the
gem. This prevents Rails getting loaded early, and getting confused.
|
| |
|
|
|
|
| |
Uncomment the test and production sections.
|
|
|
|
|
| |
Using the Rails generator seems to generate quite a lot of unnecessary
files...
|
|
|
|
|
| |
Unless running in the production environment. This helps with
development as errors are caught earlier.
|
|
|
|
| |
Also annotate existing models.
|
|
|
|
| |
And various other views and routes.
|
| |
|
|
|