Skip to content
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.

Gitlab Pages: /public cannot be used for the publicly present files. #460

Open
1 task done
gtsatsis opened this issue Jan 19, 2020 · 2 comments
Open
1 task done
Assignees
Labels
bug Something isn't working enhancement New feature or request pinned Important Issues
Milestone

Comments

@gtsatsis
Copy link

  • I confirm that this is a issue rather than a question.

Bug report

Version

0.5.0

Steps to reproduce

  • Create a Gitlab repository using the example in the examples directory.
  • Trigger CI/CD.

What is expected?

The /public/ path to be accessible and modifiable inside of a repository.

What is actually happening?

In Gitlab, /public/ cannot be used, as statusfy will error out.

Specifically, the issue is with the part where -d public is specified to replace /dist, as Gitlab requires that the deployment folder is named public, as such, the statusfy client errors out because it cannot create the distribution files in the directory it already uses to pull the public/accessible files from.

Other relevant information

A solution could be to add a flag to specify the /public folder location, such as --public ./accessible_files.

  • Your OS: nodejs:latest - Gitlab CI
  • Node.js version: nodejs:latest - Gitlab CI
  • Browser version: Chrome for Android - 79.0.3945.116
  • Is this a global or local install? Global / Gitlab Pages
  • Which package manager did you use for the install? Yarn.
@welcome
Copy link

welcome bot commented Jan 19, 2020

Thanks for opening this issue, a maintainer will get back to you shortly! Be sure to follow the issue template! 🤓

@open-collective-bot
Copy link

Hey @gtsatsis 👋, Thank you for opening an issue.

Check out our OpenCollective and consider backing us. Help us to continue developing this Amazing Project, we will appreciate it ❤️.

You can contribute from $2 🤓, less than a cup of coffee ☕ 😃

https://opencollective.com/statusfy

PS.: We offer priority support for all backers. Don't forget to add priority label when you start backing us 😄

@juliomrqz juliomrqz added enhancement New feature or request pinned Important Issues labels Feb 3, 2020
@juliomrqz juliomrqz added the bug Something isn't working label May 20, 2020
@juliomrqz juliomrqz added this to the 1.0.0 milestone May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working enhancement New feature or request pinned Important Issues
Projects
None yet
Development

No branches or pull requests

3 participants