All the information that's displayed on the "Pricing" page lives in the database.
Loading the VM sizes from the DB, like the supported operating systems, means less repeating-yourself: if you change the size options in the database, it'll immediately update the pricing page.
I went with a table because I couldn't work out how to do precise text alignment within the <pre> tags using Jinja, but there probably is a way. Anyway, it looks a little different:
I used the already-existing <table class="small"> style.
All the information that's displayed on the "Pricing" page lives in the database.
Loading the VM sizes from the DB, like the supported operating systems, means less repeating-yourself: if you change the size options in the database, it'll immediately update the pricing page.
I went with a table because I couldn't work out how to do precise text alignment within the `<pre>` tags using Jinja, but there probably is a way. Anyway, it looks a little different:

I used the already-existing `<table class="small">` style.
All the information that's displayed on the "Pricing" page lives in the database. (except for hard disk size, which isn't yet configurable)
Ah yes, correction:
> All the information that's displayed on the "Pricing" page lives in the database. **(except for hard disk size, which isn't yet configurable)**
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
All the information that's displayed on the "Pricing" page lives in the database.
Loading the VM sizes from the DB, like the supported operating systems, means less repeating-yourself: if you change the size options in the database, it'll immediately update the pricing page.
I went with a table because I couldn't work out how to do precise text alignment within the
<pre>tags using Jinja, but there probably is a way. Anyway, it looks a little different:I used the already-existing
<table class="small">style.💯
@@ -9,0 +25,4 @@<td>${{ vm_size['dollars_per_month'] }}</td><td>{{ vm_size['vcpus'] }}</td><td>{{ vm_size['memory_mb'] }}</td><td>25G</td>Still hard-coded?
Ah yes, correction:
I'm forest johnson and I approve this message