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

Using Grav with Google App Engine #34

Closed
Simple-Complexity opened this issue Aug 26, 2014 · 6 comments
Closed

Using Grav with Google App Engine #34

Simple-Complexity opened this issue Aug 26, 2014 · 6 comments
Labels

Comments

@Simple-Complexity
Copy link

Any input on using grav with Google App Engine (GAE), such as how should the app.yaml file look?

Also I get an APC cache error using the problems plugin, I will post more when I get home.

@rhukster
Copy link
Member

Unfortunately as far as I know, the most basic requirements of Google App Engine is that it can't write to the filesystem at all. You must use their data-store for any dynamic and changing aspects. As Grav is entirely file-based I don't see how it would be possible to get it running on GAE.

Please open up a new issue for your APC cache error problem. Thanks!

@Simple-Complexity
Copy link
Author

Thanks rhukster, I'll try anyway just for the heck of it. Does base Grav write to the file system or is it all the plugins that do the writing?

@rhukster
Copy link
Member

The grav base writes to the filesystem, although it is possible to override almost any aspect of Grav now we have our Dependency Injection container. Very advanced stuff though.

@Simple-Complexity
Copy link
Author

Yea, im coming from writing android apps, so I'm just starting to learn web development and php, so probably too much for me at the moment. I'll try using Heroku and see how that goes. Thanks, closing this question.

@mahagr
Copy link
Member

mahagr commented Aug 27, 2014

Just a side note: it should be pretty simple to change file functions for pages (and other dynamic data) to save into database instead of files. You just need to create a stream wrapper class, register it and change user/, cache/, logs/, assets/ and images/ to point into that wrapper. There is still some work required to make this happen, but for me it is an important goal or milestone as it opens a lot of new options -- maybe even this one.

@NastuzziSamy
Copy link

I would love to know @rhukster if their is any update here :)

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

No branches or pull requests

4 participants