2 Sep
2014
2 Sep
'14
3:59 p.m.
Hey all,
What do ya'll think about setting up a couple of development VPSs from the
sudo mesh budget?
I'd like to go for one or two of something like this:
- http://www.ftpit.com/
- ~$2 / mo for (either)
- 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1
IPv4 | OpenVZ & SolusVM
- 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB Bandwidth |
1 IPv4 | OpenVZ & SolusVM
I'm putting some attention in on the exitnode provisioning (and therefore
server provisioning in general).
I was thinking about setting up some in-person machines at sudo room for
developer training, development environments, testing before deployment,
etc. Marc pointed out that the power consumption of such a machine would
probably not be worth it given the low cost of a VPS. However, I still want
to streamline the process for facilitating new developers to build a
smaller version of peoplesopen.net network, and to provide testing
infrastructure to maintain reliability and up-time.
I updated this page on the wiki, please contribute:
https://sudoroom.org/wiki/Virtual_Private_Server
// Matt
2 Sep
2 Sep
4:47 p.m.
Hi Matt.
We should use real VMs, which means Xen or KVM (no OpenVZ and no SolusVM).
I recommend digitalocean even though they're a bit more expensive :)
On Tue, Sep 2, 2014 at 3:59 PM, Matthew Senate <mattsenate(a)gmail.com> wrote:
Hey all,
What do ya'll think about setting up a couple of development VPSs from the
sudo mesh budget?
I'd like to go for one or two of something like this:
- http://www.ftpit.com/
- ~$2 / mo for (either)
- 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1
IPv4 | OpenVZ & SolusVM
- 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB Bandwidth
| 1 IPv4 | OpenVZ & SolusVM
I'm putting some attention in on the exitnode provisioning (and therefore
server provisioning in general).
I was thinking about setting up some in-person machines at sudo room for
developer training, development environments, testing before deployment,
etc. Marc pointed out that the power consumption of such a machine would
probably not be worth it given the low cost of a VPS. However, I still want
to streamline the process for facilitating new developers to build a
smaller version of peoplesopen.net network, and to provide testing
infrastructure to maintain reliability and up-time.
I updated this page on the wiki, please contribute:
https://sudoroom.org/wiki/Virtual_Private_Server
// Matt
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
4:54 p.m.
If you just need linux boxen, we could provision some in kc. Y'all could maybe toss us
some of what you'd pay digital ocean, but if not no big.
imw
Composed on a pocket computer -- plz forgive brevity and auto correct ions.
On September 2, 2014 6:47:56 PM CDT, Marc Juul <juul(a)labitat.dk> wrote:
Hi Matt.
We should use real VMs, which means Xen or KVM (no OpenVZ and no
SolusVM).
I recommend digitalocean even though they're a bit more expensive :)
On Tue, Sep 2, 2014 at 3:59 PM, Matthew Senate <mattsenate(a)gmail.com>
wrote:
Hey all,
What do ya'll think about setting up a couple of development VPSs
from the
sudo mesh budget?
I'd like to go for one or two of something like this:
- http://www.ftpit.com/
- ~$2 / mo for (either)
- 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth |
1
IPv4 | OpenVZ & SolusVM
- 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB
Bandwidth
| 1 IPv4 | OpenVZ & SolusVM
I'm putting some attention in on the exitnode provisioning (and
therefore
server provisioning in general).
I was thinking about setting up some in-person machines at sudo room
for
developer training, development environments,
testing before
deployment,
etc. Marc pointed out that the power consumption
of such a machine
would
probably not be worth it given the low cost of a
VPS. However, I
still want
to streamline the process for facilitating new
developers to build a
smaller version of peoplesopen.net network, and to provide testing
infrastructure to maintain reliability and up-time.
I updated this page on the wiki, please contribute:
https://sudoroom.org/wiki/Virtual_Private_Server
// Matt
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
!DSPAM:5406573189101042447563!
------------------------------------------------------------------------
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
!DSPAM:5406573189101042447563! 
6:22 p.m.
We have at least one shared dev vps already, and I have one personally that I've been
hacking on at digital ocean. If anyone wants to use digital ocean, I can send them a $10
credit and get $25 credit myself....
On September 2, 2014 3:59:26 PM PDT, Matthew Senate <mattsenate(a)gmail.com> wrote:
Hey all,
What do ya'll think about setting up a couple of development VPSs from
the
sudo mesh budget?
I'd like to go for one or two of something like this:
- http://www.ftpit.com/
- ~$2 / mo for (either)
- 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1
IPv4 | OpenVZ & SolusVM
- 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB Bandwidth |
1 IPv4 | OpenVZ & SolusVM
I'm putting some attention in on the exitnode provisioning (and
therefore
server provisioning in general).
I was thinking about setting up some in-person machines at sudo room
for
developer training, development environments, testing before
deployment,
etc. Marc pointed out that the power consumption of such a machine
would
probably not be worth it given the low cost of a VPS. However, I still
want
to streamline the process for facilitating new developers to build a
smaller version of peoplesopen.net network, and to provide testing
infrastructure to maintain reliability and up-time.
I updated this page on the wiki, please contribute:
https://sudoroom.org/wiki/Virtual_Private_Server
// Matt
------------------------------------------------------------------------
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
7:11 p.m.
In case anyone is itching to hook me up with $25 in digital ocean credits...
https://www.digitalocean.com/?refcode=4179646e1e52
On Tue, Sep 2, 2014 at 6:22 PM, Max B <maxb.personal(a)gmail.com> wrote:
We have at least one shared dev vps already, and I
have one personally
that I've been hacking on at digital ocean. If anyone wants to use digital
ocean, I can send them a $10 credit and get $25 credit myself....
On September 2, 2014 3:59:26 PM PDT, Matthew Senate <mattsenate(a)gmail.com>
wrote:
> Hey all,
>
> What do ya'll think about setting up a couple of development VPSs from
> the sudo mesh budget?
>
> I'd like to go for one or two of something like this:
>
>
> - http://www.ftpit.com/
> - ~$2 / mo for (either)
> - 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1
> IPv4 | OpenVZ & SolusVM
> - 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB
> Bandwidth | 1 IPv4 | OpenVZ & SolusVM
>
>
> I'm putting some attention in on the exitnode provisioning (and therefore
> server provisioning in general).
>
> I was thinking about setting up some in-person machines at sudo room for
> developer training, development environments, testing before deployment,
> etc. Marc pointed out that the power consumption of such a machine would
> probably not be worth it given the low cost of a VPS. However, I still want
> to streamline the process for facilitating new developers to build a
> smaller version of peoplesopen.net network, and to provide testing
> infrastructure to maintain reliability and up-time.
>
> I updated this page on the wiki, please contribute:
> https://sudoroom.org/wiki/Virtual_Private_Server
>
> // Matt
>
> ------------------------------
>
> mesh mailing list
> mesh(a)lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/mesh
>
>
3536
days inactive
3537
days old
4 comments
4 participants
participants (4)
-
imw -
Marc Juul -
Matthew Senate -
Max B