Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Discourse - problem installing plugins

    Discourse
    3
    5
    356
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jimmmmy last edited by

      Hi cloudron community,

      It may sound like a supernoob question. But I still have no clue about the answer.
      I have a discourse installed here
      When I try to install a plugin and run the following lines in the app's terminal:

      cd /app/code/plugins
      git clone <plugin-repo>
      cd /app/code
      bundle exec rake plugin:install_gems['REPLACE_WITH_PLUGINS_NAME'] 
      

      Everything works well.
      But when I try to run the last line of command

      rm -rf /run/discourse/public/assets/*
      

      the site goes down and the app doesn't work anymore.
      Why ? And how should I do ?

      jdaviescoates 1 Reply Last reply Reply Quote 0
      • jdaviescoates
        jdaviescoates @jimmmmy last edited by

        @jimmmmy does the site come back up after you restart the app? Sounds like that is the last step.

        Restart the application for the assets to get re-built.

        https://docs.cloudron.io/apps/discourse/

        I use Cloudron with Gandi & Hetzner

        BrutalBirdie J 2 Replies Last reply Reply Quote 1
        • BrutalBirdie
          BrutalBirdie Staff @jdaviescoates last edited by

          Exactly, did you read this line above?
          https://docs.cloudron.io/apps/discourse/

          # the line below will force assets to be rebuilt on next application restart
          rm -rf /run/discourse/public/assets/*
          

          Like my work? Consider donating a beer 🍻 Cheers!

          J 1 Reply Last reply Reply Quote 1
          • J
            jimmmmy @jdaviescoates last edited by

            @jdaviescoates thank you for your answer. It seems after further inquiries that it was due to a cache problem. I went over it again and all went well.

            1 Reply Last reply Reply Quote 3
            • J
              jimmmmy @BrutalBirdie last edited by

              @brutalbirdie yes, thanks 😊

              1 Reply Last reply Reply Quote 2
              • First post
                Last post
              Powered by NodeBB