how do I install the extension offline?

xiaoshidetaikuai

I use docker-flarum to install on my company intranet, how can I install the extension offline?

luceos

If you have no internet connection you cannot install extensions.

You could install them on a machine that has internet, then copy them over using USB. But all requirements should preferably be identical on the server versus computer.

Regardless of that, the docker-flarum image does not restrict internet access, not sure you are implying that.

xiaoshidetaikuai

luceos @clarkwinkelmann Thanks for the reply. I have a server with access to the internet, I installed the image with docker and installed the plugin, then I used docker save to export the .tar and copied the .tar to a machine without an internet connection, and after installing it, I found out that it didn't contain the plugin that I had installed on the extranet, and I didn't find any tutorials on how to migrate the plugin to the intranet and install it!

clarkwinkelmann

How does that Docker image downloads Flarum? Are the files just "hard-coded" in the image?

Whether or not you install extensions, you need a strategy to update Flarum itself in case of any security fix. Whatever solution is used to update Flarum can probably be leveraged to install extensions as well.

If you're building your own Docker image, just install more packages in the build process so they are available offline. If you have a Packagist proxy or offline repo using Satis, include the extensions and their dependencies in the whitelist.

But as Luceos asks, are you really offline? Being in an intranet does not imply no internet access, you can probably whitelist what's needed without any additional software(?)

luceos

Although I am not familiar with the docker-flarum image the docker save command, it seems this command can only save tagged images. Did you tag an image after making your modifications?

xiaoshidetaikuai

luceos Thank you very much for your reply, I realised that what I exported was just the image and not the container where the plugin is installed, I tried to export the container and deployed it to a machine that doesn't have access to the internet and it ran successfully!