Please investigate integrations for:
Lucid Link
Hammerspace
WekaIO
TrueNAS
Please help demystify:
masv-portal
the command suggests using masv_portal but the compiled code uses masv-portal?
MASV-API/Portals
I am unable to create a portal using the supplied curl command since the TEAM_ID receives error 404
Hey Phil, I’m so sorry for the delay.
Hammerspace, Weka, and TrueNAS are noted.
With Lucidlink announcing their API in the new year we are ready to pounce as soon as they open it up for us. One of our most requested features so as soon as they open up the gates and let us in we’ll get to work!
I’m looking in to your issues right now.
@MASV_Conner, @randy - Great News Conner, thanks for the follow-up.
Hey Phil,
Thanks for catching our typo. We’re updating the documentation to reference masv-portal instead of masv_portal.
Regarding your curl command issue, Portal creation can be simplified using the npm/node module.
npx masv-portal new --name logikportal --message "logik test portal" --subdomain logiktest --recipients conner@masv.io
The help can be listed with the -h/--help flag.
npx masv-portal new -h
Usage: masv_portal new [options]
Create new Portal
Options:
--subdomain <string> Subdomain of the Portal to create
--name <string> Name of the Portal to create
--message <string> Message displayed on the Portal upload page
--recipients <email...> Email address(es) that will receive notification of uploads
-t, --team <id> Team ID. Default: MASV_TEAM environment variable
--access_code <string> Password to upload packages to this Portal
--download_password <string> Password for downloading packages from this Portal
--tag <string> Name of tag to associate with all packages from this Portal
-h, --help display help for command
Our GitHub should have an example of how to create a portal
masv_portal new \
--name "My New Portal" \
--message "Welcome to my new Portal!" \
--subdomain mynewportal \
--recipients "edwina@example.com" \
--tag "JOB-2024-03"
If you have any more questions, please shoot an email over to support@masv.io, and please CC me at conner@masv.io
@MASV_Conner - thanks Conner.
I’ll try the new code and let you know how I get on with it.
Thanks to you and the team for following up and fixing.
Happy Monday Brother
Happy Monday Phil, hit me up any time!
+1 for direct lucid access
i have built something around lucid that does kinda the same , its doable without the API just not at scale, requires mounting the filespace on a virtual machine instance and then doing normal fileoperations on this vps.
I am sure you could run this highly automated but yea direct access makes way more sense if thats on the horizon
That’s definitely a workflow that I’ve recommended in the past. Not ideal but it gets the job done. The goal is always to remove the friction for file transfer and it will be great to have less friction with such a popular tool.
2025 is going to be an exciting year with lots on the horizon!