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

Give DW Access to Gogs RDS #133

Closed
2 tasks done
jag3773 opened this issue Jan 9, 2017 · 1 comment
Closed
2 tasks done

Give DW Access to Gogs RDS #133

jag3773 opened this issue Jan 9, 2017 · 1 comment
Assignees
Labels

Comments

@jag3773
Copy link
Contributor

jag3773 commented Jan 9, 2017

Since DokuWiki uses the Gogs database for user management we need to ensure that the DW server has access to the RDS instance.

Notes

  • Verify that queries do not need changed in DW admin interface (e.g. table name changes)
  • Create user and grant privileges

The testing portion is moved into #122

@jag3773 jag3773 added the Gogs label Jan 9, 2017
@jag3773 jag3773 self-assigned this Feb 13, 2017
@jag3773 jag3773 mentioned this issue Feb 14, 2017
3 tasks
@jag3773
Copy link
Contributor Author

jag3773 commented Feb 14, 2017

Completed by running these commands on database server:

CREATE USER 'user'@'ip' IDENTIFIED BY 'some_pass';
GRANT ALL ON `gogs`.user TO 'user'@'ip' WITH GRANT OPTION;
GRANT ALL ON `gogs`.team TO 'user'@'ip' WITH GRANT OPTION;
GRANT ALL ON `gogs`.team_user TO 'user'@'ip' WITH GRANT OPTION;

Obviously, I've masked the user, ip, and pass fields 😉

@jag3773 jag3773 closed this as completed Feb 14, 2017
richmahn pushed a commit that referenced this issue Jun 13, 2023
See [Defining outputs for
jobs](https://docs.github.com/en/actions/using-jobs/defining-outputs-for-jobs)
and [Example usage of the needs
context](https://docs.github.com/en/actions/learn-github-actions/contexts#example-usage-of-the-needs-context).

Related to:
- [actions-proto-def
#5](https://gitea.com/gitea/actions-proto-def/pulls/5)
- [act_runner #133](https://gitea.com/gitea/act_runner/pulls/133)

<details>
<summary>Tests & screenshots</summary>

Test workflow file:
```yaml
name: outputs
on: push

jobs:
  job1:
    runs-on: ubuntu-latest
    outputs:
      output1: ${{ steps.step1.outputs.output1 }}
      output2: ${{ steps.step2.outputs.output2 }}
    steps:
      - name: step1
        id: step1
        run: |
          date -Is > output1
          cat output1
          echo "output1=$(cat output1)" >> $GITHUB_OUTPUT
      - name: step2
        id: step2
        run: |
          cat /proc/sys/kernel/random/uuid > output2
          cat output2
          echo "output2=$(cat output2)" >> $GITHUB_OUTPUT
  job2:
    needs: job1
    runs-on: ubuntu-latest
    steps:
      - run: echo ${{ needs.job1.outputs.output1 }}
      - run: echo ${{ needs.job1.outputs.output2 }}
      - run: echo ${{ needs.job1.result }}
```

<img width="397" alt="image"
src="https://user-images.githubusercontent.com/9418365/233313322-903e7ebf-49a7-48e2-8c17-95a4581b3284.png">
<img width="385" alt="image"
src="https://user-images.githubusercontent.com/9418365/233313442-30909135-1711-4b78-a5c6-133fcc79f47c.png">



</details>

---------

Co-authored-by: Giteabot <teabot@gitea.io>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant