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

Mount Android keystores #4

Open
snoopdouglas opened this issue Dec 16, 2024 · 2 comments
Open

Mount Android keystores #4

snoopdouglas opened this issue Dec 16, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@snoopdouglas
Copy link
Member

snoopdouglas commented Dec 16, 2024

This is to enable Android exports. Though it'd be possible by adding volumes and a pre-script in the config, it'd be ugly - far better to do it automatically.

We'll need to interrogate two files for this: export_presets.cfg, which can override per preset, and the user's editor_settings*.tres.

In the case of nothing being set up in the user environment, don't throw an error - this'll be a likely scenario in CI. A keystore is more likely to be pre-configured for Godot on a workstation because of one-click deploy.

Note we'll possibly want to consider this for other export fields which require things strewn around the FS.

@snoopdouglas snoopdouglas added the enhancement New feature or request label Dec 16, 2024
@snoopdouglas
Copy link
Member Author

snoopdouglas commented Dec 19, 2024

Edit this won't work, as we need the user and password too.


Scrap that, I'm just going to provide well-known locations instead. This should reduce complexity all round, at the cost of a bit of magic (some would say this is 100% a good thing).

In the docs, we'll suggest users mount keys like:

  • ...:/srv/android/debug.keystore:ro
  • ...:/srv/android/release.keystore:ro

@snoopdouglas snoopdouglas self-assigned this Dec 19, 2024
@snoopdouglas
Copy link
Member Author

nb. keystore path and user/pass overrides are stored in src/.godot/export_credentials.cfg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant