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

Clarify hardware requirements in the installation guide #4983

Closed
AyaMorisawa opened this issue May 25, 2019 · 3 comments
Closed

Clarify hardware requirements in the installation guide #4983

AyaMorisawa opened this issue May 25, 2019 · 3 comments
Labels
📖Doc Documentation related issue/PR

Comments

@AyaMorisawa
Copy link
Contributor

@syuilo I think this information should be documented to the installation guide.

Originally posted by @acid-chicken in https://github.com/syuilo/misskey/issues/4826#issuecomment-488282853

@AyaMorisawa AyaMorisawa added the 📖Doc Documentation related issue/PR label May 25, 2019
@u1-liquid
Copy link
Sponsor Contributor

The memory specification problem is actually due to the peak at the time of WebPack build,
Therefore, there are likely to be many differences in memory specifications between what is required for actual operation and what is required for build.
I can say if server have 2GB of RAM, it will be enough to build and running both Misskey and Mastodon instance with running PostgreSQL, Redis, Ai-Chan on same machine.

@sftblw
Copy link
Contributor

sftblw commented May 27, 2019

IMHO, with fairy enough swap for webpack build, 1GB is fine or minimum requirement to run misskey.
my instance runs misskey (install), elasticsearch for misskey, gitea (docker - barely used), nginx on 1GB arch linux VPS.

Previously I set swap file as 2GB but that was not enough. I think 3~4GB swap would be appropriate. I experienced "Can't Build" when It was v10 and after that set up automated swap allocation, and the problem fixed.

@tamaina
Copy link
Contributor

tamaina commented Jun 24, 2022

hubマター

@tamaina tamaina closed this as completed Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📖Doc Documentation related issue/PR
Projects
None yet
Development

No branches or pull requests

4 participants