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

Jump to bottom

[doc] Document file system behavior #101

Merged
merged 1 commit into from Mar 29, 2013
Merged

[doc] Document file system behavior #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 7 additions & 0 deletions content/a-quickstart/faq.md
View file
Open in desktop
Expand Up @@ -254,4 +254,11 @@ more drones to fit your needs.
We always provision a new virtual machine. The old one gets decommissioned if We always provision a new virtual machine. The old one gets decommissioned if
and only if everything went ok, so a failed deploy does not equate to down time. and only if everything went ok, so a failed deploy does not equate to down time.


---

## Can I write to the file system? What are the limits?

File system on our virtual machines is both readable and writable, but does not
persist across deploys. Capacity of the file system is 3 GB.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3? I thought you said it was 5 ;p?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actual disk size is 5 GB, but we would like our users to keep their files down to 3 GB (we store logs and such which can take some space).


[meta:title]: <> (FAQ) [meta:title]: <> (FAQ)