Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Funding Request: WICit Hosting #26

Open
roughani opened this issue Nov 10, 2014 · 4 comments
Open

Funding Request: WICit Hosting #26

roughani opened this issue Nov 10, 2014 · 4 comments

Comments

@roughani
Copy link
Contributor

We've been paying to host WICit on Amazon Web Services. Total expenditures to date have been approximately $300. We've made efforts to reduce monthly hosting costs to approximately $30, but we would love for a community partner to step-up and help us sustain the platform with $1,000 annually so that we can feel confident in scaling the application and adding additional features. If you're interested, please drop us a line at hello [at] codeforsacramento [dot] org. Or comment below.

@marks
Copy link

marks commented Jan 26, 2015

@roughani - great app. I work for Socrata and came across this a while ago but recently came back to see what's happened lately. Related to this issue, I wonder if you all have looked into making it completely client-side and simply hosting it on AWS S3 (and even with CDN in front of it)? It appears to call the SODA APIs on the client side as-is.

Just curious if this is something I could potentially help y'all out with. Still hope you get funding to help with future development!

@roughani
Copy link
Contributor Author

@marks thanks. I think we went with a server-side architecture because the API was only available temporarily during a beta phase and then went dark for a week or two before CDPH officially launched their open data portal. The good news is @jesserosato migrated the app to DigitalOcean yesterday, so now it's only going to cost us $5/mo. We have additional features planned, so I'll defer the issue to Jesse re: making it completely client-side.

@jesserosato
Copy link
Contributor

Hey @marks, thanks a lot for taking a look at the project and for your suggestions! I think definitely think wicit could work as a completely client-side application. TBH, I didn't even think about that option when I started building (wicit started as an excuse to play with node, which turned into an excuse to play with angular...), but it's a really good idea! We're looking at a couple of features long term that will need to live on a server, but I'd like to isolate those as APIs anyways. I don't have time to do any of this right now, but if anyone out there wants to fork and take a run at it, I'd be happy to go that direction.

@jesserosato
Copy link
Contributor

Keeping this open, as securing long-term funding/maintenance for deployed Code for Sacramento projects remains an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants