Twitter

Website URL

Jabber

Location

Interests

I own a Powerpack licence which I have been using for some time on my Mac Min and I have recently been given a Macbook Air and would like to also use Alfred Powerpack on this machine, is this possible without buying a second licence and if so how do I download and insert the licence code into the app on the Macbook Air?

Hi guys,
I saw that there are already 2 different Doprobx workflows. Unfortunately, I don't think they're really convenient:
"Dropbox Short Links" (here) is able to get the link of any file located in the Dropbox folder, but doesn't work with a file that's not in the Dropbox folder. You have to copy/move the file manually then run the workflow.
"To Dropbox 3.0" (here) is able to copy/move any file to Dropbox and get a public link, but works only with the Dropbox "Public" folder (which is a bit deprecated).
I think that the Ultimate Dropbox sharing workflow would allow:
To copy a random file to a specific Dropbox folder (e.g. "Shared Files") To generate a direct/share link for that file
I am not a developer so anything related to Ruby is really hard to understand and I am not able to develop/write such a workflow I need... Does anybody out there have some time to do it? I know I ask a favor here, but I'm sure you'll do 20 times faster than me. :-)
Thanks!

Greetings, Alfred Community,
I use several cloud file sync apps like Dropbox, GDrive, Evernote, and Box.com.
Most of these tools add a context menu to my desktop Finder window, allowing me to instantly share a file and copy the share URL to the clipboard.
I love to use Alfred to FIND all those files quickly on my desktop, but it would be awesome to be able to copy a share URL right from Alfred instead of doing "Show in Finder" and right-clicking the context menu. First world problems, I know, but we're all about speed in here, and this would make many of us extra speedy....
Thanks for reading!
Ted

Web Server
Easily start a web server and add files to it (v 1.3.6)
------------------------------------------
Update 1.3.6:
- Port number wasn't copying to clipboard when checking the IP Address.
Update 1.3.5:
- New and Better IP addresses checker. My Thanks and Credits to Shawn Rice.
- Now php.ini and index.php files are hidden as well.
- Fixed some other bugs. I hope the initial setup works properly now.
Update 1.3.4:
- Uploads won't overwrite existing file with same name anymore.
- Moved user defined port file to Workflow data storage.
Update 1.3.3:
- Auto-refresh page after upload is completed!
- New notification banner saying "Upload Completed". Yay.
Update 1.3.2:
- Upload feature revamped. Now you can Drag and Drop files and then upload You can even rename them before uploading.
- It seems PHP has upload and memory limit. So uploading big files wasn't working. Hopefully everything works now. Or at least 2GB files.
Update 1.3.1:
- HUGE mistake. Sorry. The last update wasn't copying the new files to the Server folder.
Update 1.3:
- Added ability to Upload files
- Now you can check your Local and External IP addresses
- Set the Server Port number to any Port you want
Update 1.2.1:
- ***CRITICAL*** Fixed huge typo bug. The server wouldn't stop if your local IP address didn't start with "10"
Update 1.2:
- Fixed an issue with the File Action "Add Files to Web Server".
Update 1.1:
- Changed Server folder location to Workflow Data storage. (Thanks, Shawn)
- Added Readme content.
------------------------------------------
Requirements:
- Mavericks or any prior OS X with PHP 5.4
Description:
The default server's port is set to 21025. To access the web server folder, open your browser and go to your local IP address at the mentioned port. Example: "10.0.1.5:21025"
You can access your Web Server folder from any computer in the same network. If you want people from outside your local network to be able to access your Web Server folder, you have to clear the port in your router's settings (Google "port forwarding"). After clearing the port, use your external IP address instead of your local IP address. Example: "179.233.196.211:21025"
Also, the Web Server allows you or people who are accessing it to upload files, as long as the file is an allowed extension. This limitation is for security purpose.
Instructions:
+ Keywords:
- "server": Lets you start the server (if it's not running) or stop the server (if it's running).
- "server open": Open the Web Server folder. This is where you put the files you want to share.
- "add": Copy files selected in Finder to the Web Server folder.
- "server ip": Check what's your Local and External IP address.
- "set port": Set the Web Server port number to any port within the valid range of 0 and 65535, so long as it doesn't conflict with an already assigned port.
+ File Action:
- "Add Files to Web Server": Copy selected files to the Web Server folder.
Screenshots:
Download link:
https://db.tt/6HjM2lhL
Contact:
@MaximiliumM
Any feedback is welcome.

Hi there!
I've created a workflow that I want to share with my team, the workflow includes a Python script, which in turn has a dependency on a 3rd party library (the wonderful Requests[1]).
Are there any best practices around sharing this workflow with my team, whilst easing friction around the third party dependency? For example, currently I'm advocating dropping down to the command line and installing the Python dependency globally, ideally I'd like to avoid this, if at all possible.
Appreciate any pointers.
Kind regards!
Steve
[1] http://docs.python-requests.org/

Some file sharing services like CloudApp or Droplr have hard restrictions on their free plans like tiny file size limits or mandatory expiration time. These limitations made me migrate to Jumpshare, a powerful file sharing service with a generous free plan that includes:
2GB total free space, 250MB max filesize, no auto-self-destructing files;
Supports multiple files and folder uploads;
Preview over 200 file formats online without installing any software;
Real-time sharing: recipients can see upload progress; once uploading finishes, they can view the file right away;
Share via email directly from the app (with advanced options);
Expire links after x number of days, views or downloads;
Disable download so recipient can only preview the files;
Powerful In-depth Analytics dashboard;
Track shared files;
Collections and nested folders;
Jumpshare Inbox (allow anyone to send you files without signing up for an account).
Before moving to Jumpshare I used to use the nice CloudApp workflow by Carlos-Sz, so after the migration I created the following workflow which works in a similar manner.
___________________________________________________
Description
Upload files and folders to Jumpshare.
Requirements
Jumpshare installed
OS X 10.9 or later
64-bit processor
Usage
Jumpshare workflow can be used by the following actions:
Enter the keyword jmp without any argument to upload the selected items.
Enter the keyword jmp with some argument to rename and upload the selected items.
Select one or more items in Alfred and enter the file action Upload to Jumpshare.
Select one or more items in Finder and enter a custom hotkey to upload them.
Credits
This workflow is partly based on CloudApp Workflow by Carlos-Sz and uses qWorkflow Library by Ursan Razvan.
Download from Packal

Recommendations for Sharing Workflows
The forums have really been running well and you guys (and gals) have been creating some amazing workflows so far. I wanted to throw out a few suggestions though to make sure things stay organized, are easy to read, and easy to find.
This will be an evolving document. Check back for questions regarding questions on posting your workflows. If you have a question that isn't answered within the contents of this thread, feel free to contact any of the moderators (Myself, Andrew, or Vero).
Post Titles
Be specific. Don't be overly descriptive about every little feature the workflow provides. Titles are best kept to the workflow name, and potentially a few words on the overall gist of what it does.
Tags
Be sure to set topic tags for your workflow post. This will make it easier for users searching on the forums to find your post/workflow easily based off of a few key words.
Dependencies
Please include a listing of all dependencies for your workflow. This will hopefully alleviate potential problems that users run into from attempting to run an installed workflow without an installed package being present. Examples of this would be Ruby gems or Python modules or even Python versions that are required for using the workflow. If a specific application is required for your workflow to function, be sure to include a link to that applications website, or a link to it in the App Store as well. Also include, if necessary, required versions of OS X.
System Modifications
If your workflow creates or modifies any supporting files that would alter the users environment, this should be noted. This will make it known up front that your workflow modifies system file X to achieve its functionality. Also, if the user uninstalls the workflow, how to remove these files or restore the originals.
Screenshots
They aren't required, but providing a screenshot or two for your workflow helps provide users with a good idea of what it is they are about to download. Descriptions help, but many users are wanting to pop in, get a quick visual, and download.
Posting
When sharing a new workflow, please be sure to create your own thread for it. By posting it in another workflows thread, your workflow may never reach the masses. Create your own thread so that it stands out and everyone will be able to find it easily. This helps remove confusion on which workflow to download if there are multiple workflows, or modified workflows posted within the same thread. It also helps ensure that the develop that spent their time and put in the hard work to create the workflow get credit for their work. Posting a patch/update/fix/modified version of a workflow in another authors thread may steal attention from their original work. So let's try to be considerate.
Sharing Multiple Workflows
Try to limit a new thread to a single workflow. The reason for this follows the situation mentioned above. Unless you have an abnormally long title, users casually browsing the forums may not realize how many workflows are available in the post, or what they are. Creating a separate post for workflows also creates an individual area for you to provide support or answer questions for that workflow alone.
Modifying Existing Workflows
Most developers are very open to feature requests for their published workflows. So before modifying someone else's workflows, check with the developer and see if they would add the feature first. If the requested feature is something that the developer doesn't plan on adding, of course you could add the feature yourself. If you think it's a feature that others would also find greatly useful and you decide that you would like to share your modified version, please be respectful of the original developer give them a heads up before hand. Also, be courteous and give credit to the original author and/or a link back to their original thread so that they receive some credit for their work. Nobody enjoys having their work stolen.
Updating You Workflows
When sharing an update to an already posted workflow, rather than creating another post in the existing thread, update the initial post to include desired information and updated download links (if necessary). This makes it easier for users to find the most up to date version of your workflows, along with information what is included in the update. You could also modify the thread title to indicate the date that the workflow was last updated.
Notice: I'm also going to try to monitor this thread and keep it clean. If you post suggestions for other things to be added to the document, if they are merged in, I will probably remove your original post. Questions will also be treated the same way. If answers are later added into the original post, I may remove the original question. This will hopefully keep it so that all documentation remains in the original post so someone doesn't potentially have to search through several pages of questions for find a simple answer.

This one will require a little editing to share from your chosen Ethernet device.
It's currently set to share from "Display Ethernet", as I route my ethernet through my display.
http://cl.ly/3h0H332q0H0l
matt