Closed
Description
I've been working with templates a lot recently and have noticed a couple of issues with the Digital Ocean template, as well as some other things I'd like to receive some input on before attempting to fix.
Proposed Fixes
- The metadata on Line 275 of the current template is attempting to check the size of the home directory mounted to
/home/coder
, but the template creates a user based on the coder username, so that mountpoint never gets created. I intend to change this to reflect the usage of the drive mounted to/home/${data.coder_workspace.me.owner}
Suggestions Looking for Feedback
- DO has a droplet size with 1 CPU/512MB RAM, but it isn't available in all regions. For example, it is not available at nyc2 or nyc3, but it is available at nyc1.
- DO volumes, which are required for home drive persistence, is not available in all regions. For example, it is available at nyc1 and nyc3, but not nyc2.
- The 8 CPU/16GB RAM droplet isn't available until the account owner requests it and DO approves it.
In my personal configs, I have added the small droplet mentioned above, and removed all regions which do not support the small droplet or volumes. In my opinion, the example templates should strive to provide the most likely to succeed experience out of the box. With this in mind, I would like to propose the following changes:
- Drop the 8 CPU/16GB droplet as accounts created to test Coder on DO won't have this configuration.
- Drop regions which don't support volumes as one of the key feature of Coder is the ability to persist the home volume while destroying the vm when they're Stopped.
- Add the 1 CPU/215MB RAM droplet and remove regions that don't support it as this would decrease the cost to playing around with Coder in DO. I'm on board with having this one shot down because it seems like having more regions may be more advantageous than having a smaller/cheaper droplet.
If anyone has any feedback on these points or any other issues with the DO droplet, I'm more than happy to look at them when I make the PR for the things discussed above.
Metadata
Metadata
Assignees
Labels
No labels