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

Latest commits broke Shaarli #639

Closed
Jucgshu opened this issue Aug 16, 2016 · 5 comments
Closed

Latest commits broke Shaarli #639

Jucgshu opened this issue Aug 16, 2016 · 5 comments
Labels
3rd party interoperability with third-party platforms invalid question
Milestone

Comments

@Jucgshu
Copy link

Jucgshu commented Aug 16, 2016

Hi guys,

Not sure what's going on, but I'm getting a blank page with latest commits.

Resetting to commit 085157c fixes the issue.

-j


Nginx 1.10.1
Php-fpm 7.0.9
Sqlite 3.14.0

@alexisju
Copy link

It is probably the introduction of composer, as dependency manager, which broke you install.

I am very perplex about this introduction into Shaarli. I think that just broke what make the succes and the interest of Shaarli : no sql db and very easy to install on most web hosting (including shared hosting or very light servers).

@Jucgshu
Copy link
Author

Jucgshu commented Aug 16, 2016

Mmh, I should have thought of that.

Anyway, all is working now, thanks :-)

@Jucgshu Jucgshu closed this as completed Aug 16, 2016
@virtualtam
Copy link
Member

cf #607 #613

@Jucgshu using master comes with some risks & responsibilities ;-)

  • things may break
  • the commit log is your best friend

@alexisju I get your point, but we're way past the time where Shaarli was a mere 1500-line PHP hack.

We need to move forwards and adopt proper software management tools to ease our development and release work, and make the codebase modular and easy to dive-in for newcomers, which entails:

  • maintaining a proper documentation
  • having a decent unitary test coverage
  • following coding conventions
  • using a dependency management system to pin dependencies and avoid duplicating stuff everywhere (and being ashamed of it...)

Regarding this specific-point: drag-and-drop Shaarli installs, I've added a couple extra targets in #608 to the Makefile, that will enable us to generate, upload and provide full-featured Shaarli releases, i.e. containing Shaarli + third-party dependencies normally resolved through Composer.

This new release mode will be available and advertised starting with the v0.8.x series, so shared hosting users are not (too) impacted by the change.

Again, please check the following before any upgrade:

@virtualtam virtualtam added invalid question 3rd party interoperability with third-party platforms labels Aug 16, 2016
@virtualtam virtualtam added this to the 0.8.0 milestone Aug 16, 2016
@Marsup
Copy link

Marsup commented Aug 16, 2016

A quick question as I'm no php expert : would it be feasible or desirable to commit the result of composer into git ? Does composer download system-specific binaries ? From what I read it downloads everything into a vendor folder, if there's no roadblock you could commit that and still keep all the advantages you mentioned.

@virtualtam
Copy link
Member

@Marsup discussion continued @ #613 - Use Composer to manage all 3rd-party PHP libraries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party interoperability with third-party platforms invalid question
Projects
None yet
Development

No branches or pull requests

4 participants