What would have helped me was if these instructions said something like, “Hey dummy! Don’t run the git clone command from the shell. Just add the command to the app.yml file per the example, make sure the indents are correct, save it, and then run the rebuild command.”
These instructions could also be clearer when -E -u are necessary and when they are not.
I did some other dumb things to before I succeeded. When I look at the instructions now, they make nearly perfect sense. But I fell into several pitfalls that I might have avoided if these instructions were written considering noobs like me would be trying to follow them.
Hi,
Is this the only way to install plugins?
Because I am deployed in the company’s intranet environment, my access to the external network fluctuates greatly, and I often fail to access it when I execute the. /launcher rebuild app. Is there any way to download the plugins offline and then deploy it?
תודה על התשובה שלך.
מכיוון שהתחלתי לאחרונה להשתמש ב-Discourse, עדיין יש לי שאלה.
לדוגמה, עדכנתי את קובץ app.yml והוספתי תוסף, אבל נראה שבכל מצב של בנייה מחדש, גם אם זה לא הפעם הראשונה שיש לפרוס, מה שהורד והותקן לפני כן יועבר להורדה שוב?
כגון Ruby או תוספים שהותקנו.
If you’re getting disconnected while the rebuild is running, you can use tmux or screen.
It’s possible to build the container elsewhere, push it to the repo and then launch it on your site (you also need to migrate the database and precompile the assets).
אני בספק שיש דרך, הסיבות לכך שהוא מהיר ומיועד לפורומים היא שהוא בנוי מראש, לא כמו אתר רגיל שמוצג על ידי המערכת תוך כדי תנועה (אלא אם כן יש לך מטמון) אבל אתרים רגילים שמטמון לא יכולים להגיש תוכן דינמי.
Ah good observation - if someone could replace it with another suitable example, that would be helpful. I’m not that active on Meta and not up-to-date on which plugins have been added to core.
(As an aside, my interface on Meta also seems to be incredibly messed up at the moment and it’s hard to post/make edits on iPad with Arc browser - no idea what’s going on)
i would recommend creating a topic in Site feedback or UX if it were not a bug of meta. I’m aware that self-hosted categories usually require the OPs bug reports to provide details that the Discourse team don’t have access to.