-
Notifications
You must be signed in to change notification settings - Fork 17
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
WIP: Pass Twitter client secrets as build arguments #107
base: master
Are you sure you want to change the base?
Conversation
215ebbb
to
bcb9796
Compare
As I finally have some time to look at it, maybe some questions - partially already addressed in direct chat, some not. ;) In general, some automation is definitely good - always wanted to setup an automated build. However, I'd like to avoid that the Twitter client ID and secret are visible to people who just take a look at the logs or the setup files. How would this work here? Moreover, some documentation for the README how to set up the build would be needed - especially as the current Build section would become outdated with this change. |
The secrets would appear in the build logs but not
anywhere else except the qt creator usersettings for this
project which you don't upload.
I will update docs once you are ok with the functionality.
Please also test how it works for you.
|
Mhmm, not really sure then. Using GitHub Actions with built-in secrets seems to work better, see e.g. the build contributed by @jgibbon for https://github.com/Wunderfitz/harbour-fernschreiber. From my perspective there is no urgent need to invest a lot of time here then. Feel free to do so, but the thing with the secrets would be important - also when it comes to additional integrations in the future where other secrets/credentials are needed... |
This should be combined with those or we can generate the
header add build time with secrets passed to qmake. The
difference is that the build system knows about the secrets
where in the other solution its hacked into the builder.
You don't provide build logs for fernschreiber either so I
don't see the issue of having those in the log?
|
Of course, I don't provide the build log, probably wouldn't be that much beneficial... But if there is a public build, things would be different... |
Then moving them to a
generated header is sufficient.
|
86f25d3
to
d794294
Compare
I refactored the PR to use QMAKE_SUBSITUTION PR instead now this avoids having the credentails all over the build log. |
b90b44f
to
cd4d12a
Compare
cd4d12a
to
0a8a045
Compare
0a8a045
to
a43dbea
Compare
a43dbea
to
d354407
Compare
Instead of having the user to create a header file. The build arguments can be set in qt creator project settings. Signed-off-by: Björn Bidar <[email protected]>
Signed-off-by: Björn Bidar <[email protected]>
Signed-off-by: Björn Bidar <[email protected]>
Signed-off-by: Björn Bidar <[email protected]>
Signed-off-by: Björn Bidar <[email protected]>
d354407
to
2111880
Compare
Instead of having the user to create a header file.
The build arguments can be set in qt creator project settings.