I'm not much of a techie as there have been many over the head moments when experimenting with ftp's, CDN's and such. Amazon Web Service or AWS S3 seems like a cheap reliable way to publish files. Seeing that Tempshare goes that route, there must be something to it. Does anyone have Step by Step instructions on how to publish Story files to ASW to be used by an end user via web link like Tempshare provides? Could Articulate shed some light on how they set up Tempshare on ASW?
Tempshare was actually set up as a side project by one of our developers and as such is not an official or supported Articulate product. It’s just a helpful tool we’ve made available to folks who need it. In regards to the Amazon web service, you can host directly there as mentioned in this article.
I saw the article that you linked in your response, and it was that article that prompted me to look into ASW. I was hoping the person who set up the Tempshare side job with ASW could provide more details on how it was executed. Uploading to ASW is the easy part. Making it active for users via a link like how it's done with Tempshare is what stumps me. Any assistance would make a world of difference for me.
I don't know that the person who created Tempshare is still with Articulate, but hopefully someone in the community is able to share their expertise here. :-)
I've been able to open a free AWS account and have used it to publish Storyline content to share. The most difficult thing about this process is understanding what services AWS provides. Once you open an account, Amazon will send you plenty of email with links for setting up, using, and upgrading your free account.
The particular AWS you need to learn is what they call S3, which stands for Scalable Storage in the cloud. S3 is listed under the Storage & Content Delivery category.
Once your account is setup, all you need to do is logon, go to your S3 Console, create a Bucket, upload your files, make it public, then get the URL to the story.html file and share it.
The best way to learn is to try. It's free, so there's nothing to loose.
Post any specific question or problem you have after you've tried.
I appreciate you popping in to share. This thread is a bit dated and I'm not sure that Kaono still needs assistance, but your tips could certainly help someone in the future.
Ryan - I feel your pain. This is what I figured out so far, and I am by no means an expert. It just works. Like what Daniel said above. The first thing is to just get an account and sign in. Once that is done, the product that I've been using is S3. Once in there, you need to first create buckets or folders to hold your story files. I don't know the exact number of buckets you are limited to, but it's quite a bit. Within these buckets, you can insert sub-folders. I've been able to go down three levels with success. Not sure what the limit is but just understand, the more sub-folders used, the longer your link name if that matters to you. That's the easy part. Hang with me as I'll try to be clearer than mud in explaining the rest.
To post your files after it has been published. Click on a bucket that you are going to place your story files in. Once inside the chosen bucket, click on the "Actions" button located at the top of the bucket page. A drop down should appear and from that, you can select upload. Once upload is selected, a popup of sorts will appear and you'll see an area where you can drag the published SL Output folder into. I just put that whole folder and AWS will automatically create another sub-folder with the Story contents and stuff.
To get a working link out to your peeps, open the bucket or sub-folder with all of your contents and make it Public. I have no idea what this means technically, but trust me, you need to do this or else you will be pulling hairs and talking jibberish to yourself. So open the bucket showing all of your Story contents and files and select or check everything in that folder. Click on that "Actions" button at the top, and select "Make public" in the drop down. Depending on the size of your file, it may take a few minutes to process.
If you made it to this point successfully, than its all downhill from here. Once all of your story files have been made public. You will now be able to share your story. Warning, if any one of the files are not made public, you may run into issues so ensure ALL of the files are public. Now all you have to do is go back and select just the story.html file. Click on the button that says "Properties" on the top right of the page. A pop up will appear in which you will see a hot link. If everything is right, click on it and it will open your story in the browser. If that happens, celebrate with an extra shot or two of espresso or beverage of choice and share your creation to the world by copying that link and passing it out to your devoted followers.
I hope this helps. I guess now I should get some work done.Btw, I've found video files make your story a little sluggish or worse, hang up. If anyone knows a more efficient way to use AWS, please share.
Oh I forgot a very important point. When creating names for your buckets, don't use spaces between words as I've become used to with my Mac. Use the typical file naming protocol. This will keep you out of trouble.
So, I'm using SL2 - I publish, then choose the Zip Folder. Following that, I carry the zip folder over to the S3 bucket. That didn't work, and it didn't create subfolders for me either :(
I uploaded each file at a time also, made everything public, looked for the hot link for story.html, click on that link, and it still didn't work.. Hmm... Thoughts?
Mahalo Leslie as you are correct. Ryan- I did the exact same thing, but the ASW will not automatically unzip the file as does the Articulate tempshare upload. This was one of the details that I was hoping for when I posed my original question about a year ago. Without the technical coding expertise that I figured was required, I settled for placing the entire folder into the bucket. I'm sure there is a way to accomplish the zip file upload. I guess not knowing this is one of the downfalls of going the path of business major rather than a computer programming specialist. hahaha. I hope it works for you. If I can figure it out, anyone can...trust me.
20 Replies
HI Kaono,
Tempshare was actually set up as a side project by one of our developers and as such is not an official or supported Articulate product. It’s just a helpful tool we’ve made available to folks who need it. In regards to the Amazon web service, you can host directly there as mentioned in this article.
Mahalo Ashley for your response.
I saw the article that you linked in your response, and it was that article that prompted me to look into ASW. I was hoping the person who set up the Tempshare side job with ASW could provide more details on how it was executed. Uploading to ASW is the easy part. Making it active for users via a link like how it's done with Tempshare is what stumps me. Any assistance would make a world of difference for me.
I don't know that the person who created Tempshare is still with Articulate, but hopefully someone in the community is able to share their expertise here. :-)
Hi Kaono,
I've been able to open a free AWS account and have used it to publish Storyline content to share. The most difficult thing about this process is understanding what services AWS provides. Once you open an account, Amazon will send you plenty of email with links for setting up, using, and upgrading your free account.
The particular AWS you need to learn is what they call S3, which stands for Scalable Storage in the cloud. S3 is listed under the Storage & Content Delivery category.
Once your account is setup, all you need to do is logon, go to your S3 Console, create a Bucket, upload your files, make it public, then get the URL to the story.html file and share it.
The best way to learn is to try. It's free, so there's nothing to loose.
Post any specific question or problem you have after you've tried.
Hi Daniel!
I appreciate you popping in to share. This thread is a bit dated and I'm not sure that Kaono still needs assistance, but your tips could certainly help someone in the future.
yeah it is a bit dated. I have NO IDEA on how to do this... any help would be appreciated...
Hi Ryan!
Are you looking for information on Amazon Web Service,? You can host directly there as mentioned in this article.
Hi Leslie,
Sort of, I'm having a hard time posting a storyline file to S3
Hi Ryan!
Check out this post and see if the information there is helpful. This is not a service I utilize.
Ryan - I feel your pain. This is what I figured out so far, and I am by no means an expert. It just works. Like what Daniel said above. The first thing is to just get an account and sign in. Once that is done, the product that I've been using is S3. Once in there, you need to first create buckets or folders to hold your story files. I don't know the exact number of buckets you are limited to, but it's quite a bit. Within these buckets, you can insert sub-folders. I've been able to go down three levels with success. Not sure what the limit is but just understand, the more sub-folders used, the longer your link name if that matters to you. That's the easy part. Hang with me as I'll try to be clearer than mud in explaining the rest.
To post your files after it has been published. Click on a bucket that you are going to place your story files in. Once inside the chosen bucket, click on the "Actions" button located at the top of the bucket page. A drop down should appear and from that, you can select upload. Once upload is selected, a popup of sorts will appear and you'll see an area where you can drag the published SL Output folder into. I just put that whole folder and AWS will automatically create another sub-folder with the Story contents and stuff.
To get a working link out to your peeps, open the bucket or sub-folder with all of your contents and make it Public. I have no idea what this means technically, but trust me, you need to do this or else you will be pulling hairs and talking jibberish to yourself. So open the bucket showing all of your Story contents and files and select or check everything in that folder. Click on that "Actions" button at the top, and select "Make public" in the drop down. Depending on the size of your file, it may take a few minutes to process.
If you made it to this point successfully, than its all downhill from here. Once all of your story files have been made public. You will now be able to share your story. Warning, if any one of the files are not made public, you may run into issues so ensure ALL of the files are public. Now all you have to do is go back and select just the story.html file. Click on the button that says "Properties" on the top right of the page. A pop up will appear in which you will see a hot link. If everything is right, click on it and it will open your story in the browser. If that happens, celebrate with an extra shot or two of espresso or beverage of choice and share your creation to the world by copying that link and passing it out to your devoted followers.
I hope this helps. I guess now I should get some work done.Btw, I've found video files make your story a little sluggish or worse, hang up. If anyone knows a more efficient way to use AWS, please share.
Oh I forgot a very important point. When creating names for your buckets, don't use spaces between words as I've become used to with my Mac. Use the typical file naming protocol. This will keep you out of trouble.
Many thanks for the insights you've shared, Kaono! Hopefully it will be a big help to others!
Thank you so much Kaono! However, it isn't working still for some reason... :(
I used the zip folder after clicking on publish. Is this correct?
So, I'm using SL2 - I publish, then choose the Zip Folder. Following that, I carry the zip folder over to the S3 bucket. That didn't work, and it didn't create subfolders for me either :(
I uploaded each file at a time also, made everything public, looked for the hot link for story.html, click on that link, and it still didn't work.. Hmm... Thoughts?
Hi Ryan! It doesn't sound like Kaono was zipping the contents, but taking the full output folder.
Mahalo Leslie as you are correct. Ryan- I did the exact same thing, but the ASW will not automatically unzip the file as does the Articulate tempshare upload. This was one of the details that I was hoping for when I posed my original question about a year ago. Without the technical coding expertise that I figured was required, I settled for placing the entire folder into the bucket. I'm sure there is a way to accomplish the zip file upload. I guess not knowing this is one of the downfalls of going the path of business major rather than a computer programming specialist. hahaha. I hope it works for you. If I can figure it out, anyone can...trust me.
IT WORKS!!!! Thank you so much for the support Kaono and Leslie. We should have a Virtual Happy Hour sometime.
https://s3-us-west-2.amazonaws.com/interactiveresume2016/story.html
Regards,
Ryan
Glad to hear it Ryan! Thanks for popping in to update.
Ha! Nice. I know that feeling.
This discussion is closed. You can start a new discussion or contact Articulate Support.