hazaar/hazaar-warlock
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases 4 Packages Wiki Activity Actions

Warlock start scripts using composer vendor binaries #33

New issue
Closed
opened 2018-08-14 23:46:30 +00:00 by jamie · 8 comments
jamie commented 2018-08-14 23:46:30 +00:00 (Migrated from git.hazaar.io)
Copy link

I think it might be possible to supply start scripts for Warlock using composer vendor binary files.

See: https://getcomposer.org/doc/articles/vendor-binaries.md

I can add one for Linux systems and one for Windows as well.

I think it might be possible to supply start scripts for Warlock using composer vendor binary files. See: https://getcomposer.org/doc/articles/vendor-binaries.md I can add one for Linux systems and one for Windows as well.
jamie commented 2018-08-15 06:47:51 +00:00 (Migrated from git.hazaar.io)
Copy link

created branch 33-warlock-start-scripts-using-composer-vendor-binaries

created branch [`33-warlock-start-scripts-using-composer-vendor-binaries`](https://git.hazaarlabs.com/hazaar/hazaar-warlock/compare/master...33-warlock-start-scripts-using-composer-vendor-binaries)
jamie commented 2019-04-13 06:00:06 +00:00 (Migrated from git.hazaar.io)
Copy link

changed milestone to %2

changed milestone to %2
jamie commented 2019-04-15 23:29:06 +00:00 (Migrated from git.hazaar.io)
Copy link

created merge request !19 to address this issue

created merge request !19 to address this issue
jamie commented 2019-04-15 23:29:09 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !19

mentioned in merge request !19
jamie commented 2019-04-16 00:39:52 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit c5fb1112d5

mentioned in commit c5fb1112d5a5d296f2e4756b22a1af7f3c8b01d2
jamie commented 2019-04-16 01:15:40 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via commit eaf4b51fc9b0522415884ba66ee02ffcdce35ad8

closed via commit eaf4b51fc9b0522415884ba66ee02ffcdce35ad8
jamie commented 2019-04-16 01:15:40 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via merge request !19

closed via merge request !19
jamie commented 2020-04-14 23:30:33 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 6542b95ae0

mentioned in commit 6542b95ae03a40ec693712325574473ef6512d85
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.0-develop
58-restful-triggers
2.2-stable
2-warlock-to-warlock-communication
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.5
release-2.1.4
release-2.1.3
release-2.1.2
release-2.1.1
release-2.1.0
release-2.0.2
release-2.0.1
release-2.0.0
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
release-0.4.0
release-0.3.0
release-0.2.0
release-0.1.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Version 2.2
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#33
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?