Secret ENV file for Building from Source installation

[martirale]

Description

Hello, I have a question for better management of environment variables in a Homepage installation in its mode Building from source. As you may already know, when doing it with Docker the users and passwords can be placed in a .env file and referred to in the services.yaml as {{HOMEPAGE_VAR_LOREMIPSUM}}.

The problem is that in an installation like the one I performed, I don't know how to configure the .env file for it. I tried trying to implement a secrets.yaml but I don't know how to manifest it in files like services.yaml. For this reason, at the moment I have all that data placed directly in the services.yaml file as follows:

- Proxmox:
     icon: proxmox.svg
     href: 0.0.0.0:3000
     description: PVE
     widget:
         type: proxmox
         url: 0.0.0.0:3000
         username: user@pam!TokenID
         password: The token in question
         node: pve1

And as I already mentioned, the ideal would be to have it this way:

- Proxmox:
     icon: proxmox.svg
     href: 0.0.0.0:3000
     description: PVE
     widget:
         type: proxmox
         url: 0.0.0.0:3000
         username: {{HOMEPAGE_VAR_PVE_USER}}
         password: {{HOMEPAGE_VAR_PVE_KEY}}
         node: pve1

homepage version

dev (dev. Apr 4. 2024)

Installation method

Source

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

I tried setting up a .env file (and it didn't work). Then I tried a secrets.yaml file (and the same thing). Both files had this internal configuration:

HOMEPAGE_VAR_PROXMOX_USER=user@pam!TokenID
HOMEPAGE_VAR_PROXMOX_API_KEY=Token

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided and the documentation available, environment variable substitution using the {{HOMEPAGE_VAR_XXX}} syntax is supported when running Homepage within Docker. However, for a source installation, the documentation does not explicitly mention support for environment variable substitution in the same manner.

For Docker installations, environment variables are typically defined in a .env file or directly in the docker-compose.yml or docker run command. These variables are then accessible within the container and can be used in configuration files as described.

For a source installation, you would typically need to set environment variables in the environment from which you are running the Homepage application. This could be done by exporting the variables in your shell before starting the application, for example:

export HOMEPAGE_VAR_PROXMOX_USER=user@pam!TokenID
export HOMEPAGE_VAR_PROXMOX_API_KEY=Token

Then, if Homepage supports environment variable substitution outside of Docker (which is not clear from the provided documentation), it should pick up these variables and substitute them in the configuration files.

If this method does not work, it suggests that the feature may not be supported in source installations, or additional steps may be required to enable it. In such a case, you might need to look into the application's source code or contact the maintainers for guidance on how to use environment variables with a source installation.

Since the documentation does not provide clear instructions for source installations regarding environment variables, I would recommend reaching out to the Homepage community or maintainers for further assistance. You can do this by creating an issue or discussion on the Homepage GitHub repository.

This comment was generated by Glime.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.