Pages:
Author

Topic: SporeStack: Launch VPS servers with Bitcoin. Anonymous, API driven - page 5. (Read 19723 times)

legendary
Activity: 1974
Merit: 1007
Looking at your site it's interesting. But why you only sell servers for 1-28 days ? I don't understand if you are able to continue with same server after that time period (renew the contract after every 28 days for the same server) or new server is generated every time ?

28 days is the max life of any one server that I offer, by design. If you want to have them for longer, just create another one near expiry time and switch over.

Server failures are pretty inevitable so if you iron out an automated process to replace them every month it should be beneficial once you get past the annoying phase. Handling failure is a part of good infrastructure design. It also makes security patching a bit easier as you just replace the entire server.

I 100% agree with this principle. I don't necessarily agree that having temp servers is a great thing, but keeping servers up (when accounting for DDoS, traffic spikes, updates, etc.) requires redundancy, and that would, by its nature, make this fine (automated process to spin up new servers as others go down).
legendary
Activity: 3626
Merit: 4193
Thank you! Yes to both of your questions.

Still need to clean up the code more, but the client code and library is released into the public domain: https://github.com/sporestack/sporestack-python/blob/master/sporestack/nodemeup.py

Just tested it with torsocks. Seems to work fine as
Code:
torsocks nodemeup

very nice ^_^ i love it
thank you

very nice project again
legendary
Activity: 1878
Merit: 1038
Telegram: https://t.me/eckmar
Looking at your site it's interesting. But why you only sell servers for 1-28 days ? I don't understand if you are able to continue with same server after that time period (renew the contract after every 28 days for the same server) or new server is generated every time ?

28 days is the max life of any one server that I offer, by design. If you want to have them for longer, just create another one near expiry time and switch over.

Server failures are pretty inevitable so if you iron out an automated process to replace them every month it should be beneficial once you get past the annoying phase. Handling failure is a part of good infrastructure design. It also makes security patching a bit easier as you just replace the entire server.

Yeah but think about someone wanting to launch their app with your service. That person will have to migrate files and database every month and if he have somewhat decent website (decent like got some cool features) it will for sure be pain in the ass
sr. member
Activity: 391
Merit: 333
really nice project

and commandline executables is opensource?
can used under tor network?

Thank you! Yes to both of your questions.

Still need to clean up the code more, but the client code and library is released into the public domain: https://github.com/sporestack/sporestack-python/blob/master/sporestack/nodemeup.py

Just tested it with torsocks. Seems to work fine as
Code:
torsocks nodemeup
legendary
Activity: 3626
Merit: 4193
really nice project

and commandline executables is opensource?
can used under tor network?
sr. member
Activity: 391
Merit: 333
I like the web apps you make. What do you do or have you done?
Are you interested in working with startups?

Thank you!

Before Answer Market, Coinfee, and SporeStack, I've worked at Matterport, ThousandEyes, and Rackspace. A long while back I developed two Linux distributions. I'm definitely more in the infrastructure/devops realm, but I am working more and more on my development skills.

LinkedIn covers my work history pretty well: https://www.linkedin.com/in/teran-mckinney

Matterport and ThousandEyes were startups. When I joined Matterport, I was the one of two infrastructure people on the current team. I like startups, but they can be hit or miss with direction. It really depends on the mission and the people, but I don't mind a bit of chaos and starting from the ground up. I can work quickly or work well, but I prefer biasing to working well and getting things done in a way that is sustainable for the long term. I also know that sometimes you need to work fast to rush something out the door, in a pinch.

My preference is for half-time and remote, but I am open to most opportunities. Even if remote, I can travel to the office (if there is any, heh) from time to time. Especially for starting out.

I do have a phone interview today and am looking into another opportunity, but nothing has been settled or decided yet. If you're interested, please send me an email. I can give you my phone number and we can talk more from there.

I appreciate your interest! I hope that answers your question. I'm excited to talk to you if you are still interested.

Quote
Thank you for your share. It's very useful for me
I will rent some vps for sporestack.

Thank you! I'm glad to hear that. If you have a black text on white terminal you may have issues with the QR code. A reverse terminal seems to be the only one that works for that. I'm thinking about alternating QR colors to be sure one works. Not sure if there's a way I can probe the terminal for its color behavior...
full member
Activity: 168
Merit: 100
Thank you for your share. It's very useful for me
I will rent some vps for sporestack.
legendary
Activity: 854
Merit: 1000
I like the web apps you make. What do you do or have you done?
Are you interested in working with startups?
sr. member
Activity: 391
Merit: 333
Vultr's European and Asian regions have been added. Lots of small updates across the board, but I think the nodemeup's help page tells the most:

Code:
usage: nodemeup [-h] [--osid OSID] [--dcid DCID] [--flavor FLAVOR]
                [--days DAYS] [--uuid UUID]

optional arguments:
  -h, --help       show this help message and exit
  --osid OSID      Default: 230 (FreeBSD 11)
                   216: Ubuntu 16.04 i386
                   147: CentOS 6 i386
                   152: Debian 7 i386 (wheezy)
                   140: FreeBSD 10 x64
                   194: Debian 8 i386 (jessie)
                   225: Fedora 24 x64
                   193: Debian 8 x64 (jessie)
                   128: Ubuntu 12.04 x64
                   215: Ubuntu 16.04 x64
                   148: Ubuntu 12.04 i386
                   179: CoreOS Stable
                   127: CentOS 6 x64
                   234: OpenBSD 6 x64
                   139: Debian 7 x64 (wheezy)
                   167: CentOS 7 x64
                   230: FreeBSD 11 x64
                   231: Ubuntu 16.10 x64
                   232: Ubuntu 16.10 i386
                   233: Fedora 25 x64
                   160: Ubuntu 14.04 x64
                   161: Ubuntu 14.04 i386
                   162: CentOS 5 x64
                   163: CentOS 5 i386
  --dcid DCID      Default: (probably) 3 (Dallas)
                   24: Paris
                   25: Tokyo
                   39: Miami
                   12: Silicon Valley
                   19: Sydney
                   40: Singapore
                   1: New Jersey
                   3: Dallas
                   2: Chicago
                   5: Los Angeles
                   4: Seattle
                   7: Amsterdam
                   6: Atlanta
                   9: Frankfurt
                   8: London
  --flavor FLAVOR  Default: 9 (768MiB)
                   95: RAM: 4096, VCPUs: 4, DISK: 90
                   29: RAM: 768, VCPUs: 1, DISK: 15
  --days DAYS      Days to live: 1-28. Defaults to 1.
  --uuid UUID      Force a specific UUID.
sr. member
Activity: 391
Merit: 333
Looking at your site it's interesting. But why you only sell servers for 1-28 days ? I don't understand if you are able to continue with same server after that time period (renew the contract after every 28 days for the same server) or new server is generated every time ?

28 days is the max life of any one server that I offer, by design. If you want to have them for longer, just create another one near expiry time and switch over.

Server failures are pretty inevitable so if you iron out an automated process to replace them every month it should be beneficial once you get past the annoying phase. Handling failure is a part of good infrastructure design. It also makes security patching a bit easier as you just replace the entire server.
legendary
Activity: 1878
Merit: 1038
Telegram: https://t.me/eckmar
Looking at your site it's interesting. But why you only sell servers for 1-28 days ? I don't understand if you are able to continue with same server after that time period (renew the contract after every 28 days for the same server) or new server is generated every time ?
sr. member
Activity: 391
Merit: 333
Servers last from 1-28 days, but can usually be topped up. Multiple regions available, multiple Linux images and FreeBSD 11. No registration required, no IPs logged.

Pretty easy to try:

Code:
pip install  sporestack
sporestack spawn

Handy for development, quick VPNs, network test servers, or building out a whole infrastructure on microservices. Giving the servers fixed lifetimes lets you expect failure and short server life so that you develop around it.

Video demo, asciinema demo, and more information at SporeStack.com

Send me an email if you need any help integrating it: [email protected]

Thanks!
Pages:
Jump to: