serious-devs/tsuru
serious-devs/tsuru
1
0
Fork 0
Code Issues 17 Pull requests Projects 1 Releases Packages 1 Wiki Activity Actions

Update Actions for Snapcraft #5

New issue
Open
opened 2025-04-01 14:13:54 +00:00 by mlvtito · 2 comments
mlvtito commented 2025-04-01 14:13:54 +00:00
Owner
Copy link

Generate snap package with Forgejo actions.

Generate snap package with Forgejo actions.
mlvtito self-assigned this 2025-04-01 14:13:54 +00:00
mlvtito added this to the tsuru project 2025-04-01 14:13:54 +00:00
mlvtito referenced this issue from a commit 2025-05-10 21:31:29 +00:00
(CI / #5) add snapd service
mlvtito commented 2025-05-10 22:28:53 +00:00
Author
Owner
Copy link

Snap package is generated. Now we must upload the artefact and publish it on tag

Snap package is generated. Now we must upload the artefact and publish it on tag
mlvtito commented 2025-05-16 16:05:10 +00:00
Author
Owner
Copy link

I had to reserved a snap name "tsuru-sdk" instead of because of already taken "tsuru" name.
I had snapcraft "plugs" to access .local/share and .zshenv files.
An alias "tsuru" is also created.
After snap install, the user have to connect manualy,

sudo snap connect tsuru-sdk:tsuru-data
sudo snap connect tsuru-sdk:zshenv-access
sudo snap alias tsuru-sdk.tsuru tsuru

The snap name is registered but I wasn't able to publish a first version. It seems I have to wait. Once the first publication is done, I could ask for auto-alias and auto-connect in snapcraft forum : https://snapcraft.io/docs/process-for-aliases-auto-connections-and-tracks

Maybe, I should add support for Bash first to have all the plugs when I'll ask.
It would also be a good idea to ask the user if he wants the command to edit its environment or to give the line to execute by himself.

I had to reserved a snap name "tsuru-sdk" instead of because of already taken "tsuru" name. I had snapcraft "plugs" to access .local/share and .zshenv files. An alias "tsuru" is also created. After snap install, the user have to connect manualy, ``` sudo snap connect tsuru-sdk:tsuru-data sudo snap connect tsuru-sdk:zshenv-access sudo snap alias tsuru-sdk.tsuru tsuru ``` The snap name is registered but I wasn't able to publish a first version. It seems I have to wait. Once the first publication is done, I could ask for auto-alias and auto-connect in snapcraft forum : https://snapcraft.io/docs/process-for-aliases-auto-connections-and-tracks Maybe, I should add support for Bash first to have all the plugs when I'll ask. It would also be a good idea to ask the user if he wants the command to edit its environment or to give the line to execute by himself.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
tsuru
Assignees
Clear assignees
No assignees
mlvtito
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.

Blocks
#32 Add support for bash
serious-devs/tsuru
#33 Check every file access before accessing
serious-devs/tsuru
Depends on
#4 Actions with unit tests & native build
serious-devs/tsuru
Reference
serious-devs/tsuru#5
No description provided.