#Get FileSynced | Explore Tumblr posts and blogs

kaeraemarketing · 3 months ago

Text

youtube

Google Drive Masterclass: Beyond Basic Storage for Maximum Efficiency Google Drive offers secure cloud storage that lets you access your files from any device, making collaboration and file sharing seamless. Its powerful search capabilities help you find documents instantly, even when searching by content rather than filename. With built-in compatibility with Google's productivity suite, you can create, edit and share documents, spreadsheets and presentations without ever needing to download separate software. Get access to the full Gmail and Google Drive course here: https://ift.tt/rDotSj1 ✅ Important Links to Follow - Google Audit: https://ift.tt/4JlAvX1 - Google Ads Management: https://ift.tt/gwsdL3O - SEO Website Update: https://ift.tt/sPwWoQI - Visit for digital resources: https://ift.tt/Yjw3bGt - Join a free community: https://ift.tt/qevNEQO 🔔𝐃𝐨𝐧'𝐭 𝐟𝐨𝐫𝐠𝐞𝐭 𝐭𝐨 𝐬𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 𝐭𝐨 𝐦𝐲 𝐜𝐡𝐚𝐧𝐧𝐞𝐥 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐮𝐩𝐝𝐚𝐭𝐞𝐬. https://www.youtube.com/@kaeraemarketing/?sub_confirmation=1 🔗 Stay Connected With Me. Facebook: https://ift.tt/jFMbCn9 Instagram: https://ift.tt/6nfWSVv Tiktok: https://ift.tt/AhneXF7 Linkedin: https://ift.tt/SHrmBbt Pinterest: https://ift.tt/wzstqfl Website: https://ift.tt/STiCjLm 📩 For business inquiries: [email protected] ============================= 🎬Suggested videos for you: ▶️ https://youtu.be/8ld3_DuQqXg ▶️ https://youtu.be/XOYPpbh3zaY ▶️ https://youtu.be/mQJoodRwM84 ▶️ https://youtu.be/xex_HqP0QWU ▶️ https://youtu.be/p_x_ubfygfM ▶️ https://youtu.be/pFkiL4fh6o0 ▶️ https://youtu.be/00tcBgRxjAI ▶️ https://youtu.be/Lc-F8HzoyFY ▶️ https://youtu.be/poLpFGWBvFM ▶️ https://youtu.be/E8mUUvMsUmU ▶️ https://youtu.be/d-o5pv-HDFw ▶️ https://youtu.be/NTdbrijJKyM ▶️ https://youtu.be/I5sxI9RaHXY ================================= ✅ About Kelsey Flannery (KaeRae Marketing). Welcome! I’m Kelsey Flannery, also known as KaeRae, a Google Ads expert helping business owners navigate Google tools with ease. Through simple, informative videos, I provide guidance on Google Analytics, Google Ads, Google Business, Search Console, Tag Manager, YouTube Ads, Local Services Ads, Merchant Center, and more. As the owner of KaeRae Marketing, Inc., I provide results-driven marketing for home service businesses and eCommerce. Certified in key Google tools, I specialize in lead generation, PPC advertising, and online growth strategies. Let’s maximize your business’s online reach and drive real results! For Business inquiries, please use the contact information below: 📩 Email: [email protected] 🔔 Struggling with Google Analytics, Ads, or SEO? Subscribe for expert tips, effective strategies, & the best tools on PPC, lead generation, and maximizing your online reach! https://www.youtube.com/@kaeraemarketing/?sub_confirmation=1 ================================= 🔎 Related Phrases: Google Drive, cloud storage, file sharing, online collaboration, document storage, Google Docs, document backup, cloud computing, secure storage, file management, team collaboration, remote work, Google Workspace, productivity tools, file sync, cloud backup, document editing, shared folders, Google Sheets, Google Slides, file organization, data storage, digital workspace, online storage, Google Suite Hashtags #GoogleDrive #CloudStorage #FileSharing #OnlineCollaboration #DocumentStorage #GoogleDocs #DocumentBackup #CloudComputing #SecureStorage #FileManagement #TeamCollaboration #RemoteWork #GoogleWorkspace #ProductivityTools #FileSync #CloudBackup #DocumentEditing #SharedFolders #GoogleSheets #GoogleSlides #FileOrganization #DataStorage #DigitalWorkspace #OnlineStorage #GoogleSuite via Kelsey Flannery (KaeRae Marketing) https://www.youtube.com/channel/UCji8NuY6sx7RVYD85k_XJlQ March 21, 2025 at 12:15AM

#googleads #googleadwords #digitalads #ppcadvertising #digitalmarketing #businessgrowth #keywordsresearch #googlebusiness #Youtube

0 notes

digitrev · 6 months ago

Text

I'm gonna add on with my two cents about my favourite cloud backup, Backblaze. It's a paid solution (approximately $100/year or $10/month), but I've found it to be incredibly useful. It once saved my data through a total laptop destruction event. You'll want the personal backup option, in my opinion, but if you have multiple computers to manage, then the business option (same price) might be a sensible choice for you.

Advantages

Set it and forget it. Just install it and it'll start backing up your shit immediately. It automatically schedules itself to run backups on a regular basis.

You can also restrict which folders it backs up, which file types, etc...

You can store between 30 days and 1 year worth of version history with the default options. If you're willing to pay more for storage, you can get as much version history as you want. I personally recommend the 1 year option.

You can restore any file to any computer.

You have three restore options:

Download files directly in zip file archives (or individually if you want).

Create a snapshot in their paid cloud storage service (costs extra).

Have them send a USB hard drive (up to 8 TB) in the mail for an extra cost.

If you want, I'm pretty sure you can combine this with the filesync method described above and have off-site backups of your versioned files.

Disadvantages

Depending on your financial situation, this might not be the option for you.

It only runs on macOS and Windows. Sorry *nix users.

The first backup takes forever. God help you if you have a slow connection or, heaven forbid, a metered connection.

The interface for accessing your backed up files is a bit clunky and quite slow to access.

For example, the filesync method suggested above makes it very clear which files were versioned on which date. You can also see all the versions of a file in the same spot and quickly access each of them to find one that still works.

With backblaze you first have to select the point in time when you want to try to restore. Then you have to navigate through the awkward interface and download the file to see if that version is the one you want.

This is not a perfect solution. However, it does fit nicely with the 3-2-1 backup strategy (3 copies, 2 formats, 1 off-site), providing 1/3 copies, 1/2 formats, and 1/1 off-site options.

Suggested reading: Zen and the Art of IT Backup.

"versioning" your files

i have an extremely dull tutorial i want to share with you. i never think to share this advice and i think its because it's really user-unfriendly and dry. but today i can teach you how to make automated back-ups of your art files.

download freefilesync.org, a program for automating backups. its freeware and very useful if you have a lot of art to back up. everyone say "thank you freefilesync".

make a new "configuration". this is a settings file that will remember your back-up specifications.

3. make back-ups! select your files you want backed-up on the left and instruct where to put the generated back-ups on the right. save to an external drive or a google drive folder or something. just back it up! i do both just to be safest.

4. click the green gear on the top right. these are your synchronization settings. specify the type of back-ups you want. i do "mirror" because i just want them copied. you can hover over the icons for more info on what they mean to further customize your copy settings. these are mine to make basic copies.

you can also fuck around with the blue gear (where you can specify what changes should prompt the computer to make a copy) and the filter if you need to exclude something from being backed-up.

5. select "versioning" and browse/create a new folder anywhere (external drive or primary, your choice). call the new folder something that indicates the files are outdated. select "time stamp [file]" for clarity's sake.

you will now have automatic back-ups every time you make a change to your file and save it.

save your configuration settings.

6. set freefilesync to run 1x a day at a time most convenient to you using windows task scheduler. instructions here

sometimes you really fuck up a file. maybe it gets corrupted or you save it at the wrong resolution. well now you have a parachute. previous versions of your file will be saved here. every time you make a change to the file and save it, a new back-up is generated.

hopefully you will never need this.

but you might

292 notes · View notes

radiobuff81 · 4 years ago

Text

Tweeted

👍 on @YouTube: FileSynced is here - INSTALL EVERY STREAMING APP, SPORTS, MOVIES & MORE !FileSynced is here, the new Filelinked alternative for all your streaming apps ! ✅ Get FileSynced now - https://t.co/2Pq5H1vV3f ✅ Get the IPVanish offer - https://t.co/t2FhbCVbe1 ✅ …

— Chad McVeigh (@radiobuff) Jul 28, 2021

#IFTTT #Twitter

0 notes

mbaljeetsingh · 7 years ago

Text

Building CLI Applications with NodeJS

As a developer, chances are you spend most of your time in your terminal, typing in commands to help you get around some tasks.

Some of these commands come built into your Operating System, while some of them you install through some third party helper such as npm, or brew, or even downloading a binary and adding it to your $PATH.

A good example of commonly used applications include npm, eslint, typescript, and project generators, such as Angular CLI, Vue CLI or Create React App.

Shebang

This is the wikipedia definition:

In computing, a shebang is the character sequence consisting of the characters number sign and exclamation mark (#!) at the beginning of a script.

Whenever you look at any scripting file, you'll see characters such as the ones below in the beginning of the file.

#!/usr/bin/env sh #!/usr/bin/env python -c

They serve as a way for your operating system program loader will help parse the correct interpreter for your executable file. This only works in Unix Systems though.

NodeJS too has it's own supported shebang characters. Make sure you have NodeJS installed, and create a file called logger with the following content.

#!/usr/bin/env node console.log("I am a logger")

The first line tells the program loader to parse this file with NodeJS. The rest of the file is just normal JavaScript.

You can try and run the file by typing this in your terminal. You'll get a permission denied for execution.

./logger zsh: permission denied: ./logger

You need to give the file execution permissions. You can do that with.

chmod +x logger ./logger I am a logger

You'll see the file log correctly.

This could also easily be achieved if we did node logger. But we want to have our own command, and not need to use node ... to run it.

What we'll build

Now that you have a teaser, we're going to look at two example applications that we can build to learn more about CLI apps.

Quote Of The Day (qod) cli tool, that retrieves quotes of the day from https://quotes.rest/qod.

A Tiny To Do List that uses JSON to save data.

Quote of the Day

Let's create a directory and call it qod. And inside, instantiate a NodeJs app.

mkdir qod cd qod touch qod npm init -y

Next, we know we need to make requests to the quotes server, so we could use existing libraries to do just this. We'll use axios

npm install --save axios

We'll also add a chalk, a library to help us print color in the terminal.

npm install --save chalk

We then write the logic needed to retrieve these quotes. Edit the qod file.

#!/usr/bin/env node const axios = require('axios') const chalk = require('chalk'); const url = "https://quotes.rest/qod" // make a get request to the url axios({ method: 'get', url: url, headers: { 'Accept': 'application/json' }, // this api needs this header set for the request }).then(res => { const quote = res.data.contents.quotes[0].quote const author = res.data.contents.quotes[0].author const log = chalk.green(`${quote} - ${author}`) // we use chalk to set the color green on successful response console.log(log) }).catch(err => { const log = chalk.red(err) // we set the color red here for errors. console.log(log) })

The above is normal NodeJS code, and all we are doing is calling an API endpoint. Change the file permissions with

chmod +x qod

Then run the application.

./qod The best way to not feel hopeless is to get up and do something. Don’t wait for good things to happen to you. If you go out and make some good things happen, you will fill the world with hope, you will fill yourself with hope. - Barack Obama

It should appear green, as we stated with the color.

This is roughly the same as our first logger, but the point was to show that we can use existing libraries, and still run our apps the same way.

A Tiny To Do List

This will be a bit more complex, as it will involve data storage, and retrieval. Here's what we're trying to achieve.

We need to have a command called todo

The command will take in four arguments. new, get, complete, and help. So the available commands will be

./todo new // create a new todo ./todo get // get a list of all your todos ./todo complete // complete a todo item. ./todo help // print the help text

Seems straight forward.

Let's create a directory called todo, and instantiate a nodejs app

mkdir todo cd todo touch todo npm install -y

TIP - If you do a lot of creating directories and getting into the directories, you can save yourself some time by adding a function like this to your bash or zsh file.

# Create a new directory and enter it function mkd() { mkdir -p "$@" && cd "$_"; }

Then, all you need to do is type in mkd directory_name, and you'll be in there.

We'll also install chalk again, so that we can log with colors.

npm install --save chalk

The first thing we're going to do is make sure we have these commands available. To get the commands working, we'll use NodeJs' process/argv which returns a string array of command line arguments

The process.argv property returns an array containing the command line arguments passed when the Node.js process was launched

Add this to the todo file.

#!/usr/bin/env node console.log(process.argv)

Give the file executable permissions, and then run it with a new command.

chmod +x ./todo ./todo new

You're going to get this output.

[ '/Users/ganga/.nvm/versions/node/v8.11.2/bin/node', '/Users/ganga/Dev/scotch/todo/todo', 'new' ]

Notice that the first two strings in the array are the interpreter and the file full path. In this case, these are my absolute path names. Then, the rest of the array contains whatever we passed, in this case it's new.

To be safe, let's restrict these, so that we can only accept the correct number of arguments, which is one, and they can only be new, get and complete.

Modify the todo file like shown below.

#!/usr/bin/env node const chalk = require('chalk') const args = process.argv // usage represents the help guide const usage = function() { const usageText = ` todo helps you manage you todo tasks. usage: todo <command> commands can be: new: used to create a new todo get: used to retrieve your todos complete: used to mark a todo as complete help: used to print the usage guide ` console.log(usageText) } // used to log errors to the console in red color function errorLog(error) { const eLog = chalk.red(error) console.log(eLog) } // we make sure the length of the arguments is exactly three if (args.length > 3) { errorLog(`only one argument can be accepted`) usage() }

We've first assigned the command line arguments to a variable, and then we check at the bottom that the length is not greater than three.

We've also added a usage string, that will print what the command line app expects. Run the app with wrong parameters like below.

./todo new app only one argument can be accepted todo helps you manage you todo tasks. usage: todo <command> commands can be: new: used to create a new todo get: used to retrieve your todos complete: used to mark a todo as complete help: used to print the usage guide

If you run it with one parameter, it will not print anything, which means the code passes.

Next, we need to make sure only the four commands are expected, and everything else will be printed as invalid.

Add a list of the commands at the top of the code.

//.... const commands = ['new', 'get', 'complete', 'help'] //....

And then check with the passed in command after we've checked the length.

//... if (commands.indexOf(args[2]) == -1) { errorLog('invalid command passed') usage() } //...

Now, if we run the app with an invalid command, we get this.

./todo ne invalid command passed todo helps you manage you todo tasks. usage: todo <command> commands can be: new: used to create a new todo get: used to retrieve your todos complete: used to mark a todo as complete help: used to print the usage guide

We'll cover the rest of the logic in separate topics. For now, you can combine the argument checks into a single function as an exercises.

Todo App: Help Command

This is the most straight forward part of the app. All we need to do is call the usage function. Let's add this to the todo file.

//... switch(args[2]) { case 'help': usage() break case 'new': break case 'get': break case 'complete': break default: errorLog('invalid command passed') usage() } //...

We have a switch statement which will call functions based on what command has been called. If you look closely, you'll notice the help case just calls the usage function.

While writing this I also noticed that the default case can serve as an error handler for invalid commands, so I deleted the check we did earlier, and the commands array. Thought I'd leave it there because refactoring is always fun.

Todo App: New Command

The new command will create a new todo item, and save it in a json file. We will use a file db, to help us with the storage files.

The library we will use is lowdb. We could easily write functions to read and write to a json file, if we wanted to.

Install lowdb

npm install --save lowdb

Let's add [readline](https://nodejs.org/api/readline.html) and lowdb dependencies, to help us with storing data. The lowdb code is standard from their github page.

//... const rl = require('readline'); const low = require('lowdb') const FileSync = require('lowdb/adapters/FileSync') const adapter = new FileSync('db.json') const db = low(adapter) // Set some defaults (required if your JSON file is empty) db.defaults({ todos: []}).write() //...

Next, we'll add a function to prompt the user to input data.

//... function prompt(question) { const r = rl.createInterface({ input: process.stdin, output: process.stdout, terminal: false }); return new Promise((resolve, error) => { r.question(question, answer => { r.close() resolve(answer) }); }) } //...

Here we are using the readline library to create an interface that will help us prompt a user to and then read the output.

Next, we need to add a function that will be called when a user types in the new command

//... function newTodo() { const q = chalk.blue('Type in your todo\n') prompt(q).then(todo => { console.log(todo) }) } //...

We're using chalk to get the blue color for the prompt. And then we will log the result.

Lastly, call the function in the new case.

// ... switch(args[2]) { //... case 'new': newTodo() break // ... } // ...

When you run the app now with the new command, you will be prompted to add in a todo. Type and press enter.

./todo new Type in your todo This my todo aaaaaaw yeah This my todo aaaaaaw yeah

You should see something similar to this.

Notice also, that a db.json file has been created in your file system, and it has a todos property.

Next, let's add in the logic for adding a todo. Modify the newTodo function.

//... function newTodo() { const q = chalk.blue('Type in your todo\n') prompt(q).then(todo => { // add todo db.get('todos') .push({ title: todo, complete: false }) .write() }) } //...

Run the code again.

./todo new Type in your todo Take a Scotch course

If you look at your db.json, you'll see the todo added. Add two more, so that we can retrieve them in the next get command. Here's mine.

{ "todos": [ { "title": "Take a Scotch course", "complete": false }, { "title": "Travel the world", "complete": false }, { "title": "Rewatch Avengers", "complete": false } ] }

Todo App: Get Command

With knowledge from the new command, the get command should be simple to write.

Create a function that will retrieve the todos.

//... function getTodos() { const todos = db.get('todos').value() let index = 1; todos.forEach(todo => { const todoText = `${index++}. ${todo.title}` console.log(todoText) }) } //... // switch statements switch(args[2]) { //... case 'get': getTodos() break //... } //....

Running the app now, should give us this

./todo get 1. Take a Scotch course 2. Travel the world 3. Rewatch Avengers

You can make the color fancy/green by using chalk.green

TodoApp: Complete Command

The complete command is a little bit complicated.

We can do it in two ways.

Whenever a user types in ./todo complete, we could list all the todos, and the ask them to type in the number/key for the todo to mark as complete.

We can add in another parameter, so that a user can type in ./todo get, and then choose the task to mark as complete with a parameter, such as ./todo complete 1.

Since we covered how option 1 is done in the new command, we'll look at option 2.

A good problem introduced here is the ./todo complete 1, will surely surpass our validity check for the number of commands given. We therefore first need to handle this. Change the function that checks the length of the arguments with to this.

//... // we make sure the length of the arguments is exactly three if (args.length > 3 && args[2] != 'complete') { errorLog('only one argument can be accepted') usage() return } ///...

Above approach is using the truth tables, where TRUE && FALSE will equal FALSE, and the code will be skipped when complete is passed.

We'll then grab the value of the new argument and make the value of todo as completed like so

//... function completeTodo() { // check that length if (args.length != 4) { errorLog("invalid number of arguments passed for complete command") return } let n = Number(args[3]) // check if the value is a number if (isNaN(n)) { errorLog("please provide a valid number for complete command") return } // check if correct length of values has been passed let todosLength = db.get('todos').value().length if (n > todosLength) { errorLog("invalid number passed for complete command.") return } // update the todo item marked as complete db.set(`todos[${n-1}].complete`, true).write() } //...

I've made comments on each part of the code above. Please read through.

Make sure to update the switch statements.

//... case 'complete': completeTodo() break //...

When you run this with ./todo complete 2, you'll notice your db.json has changed to this, marking the second task as complete.

{ "todos": [ { "title": "Take a Scotch course", "complete": false }, { "title": "Travel the world", "complete": true }, { "title": "Rewatch Avengers", "complete": false } ] }

The last thing we need to do, is change ./todo get to only show tasks that are done. We'll use emojis for this.

//... function getTodos() { const todos = db.get('todos').value() let index = 1; todos.forEach(todo => { let todoText = `${index++}. ${todo.title}` if (todo.complete) { todoText += ' ✔ ️' // add a check mark } console.log(chalk.strikethrough(todoText)) }) return } //...

When you now type in the ./todo get you'll see this.

./todo get 1. Take a Scotch course 2. Travel the world ✔ ️ 3. Rewatch Avengers

I know, it could be improved, but you get the idea.

That's it for now.

Libraries

This is JavaScript, and of course some brilliant person out there has thought of all these and written helper libraries. The focus for this article was to look at how CLI applications are built with vanilla nodejs, but when working in the real world, it would be more productive to use libraries.

Here's a list of helpful libraries to help you write awesome CLI applications, which you can publish to npm.

vopral - fully featured interactive CLI framework

meow - CLI helper library

commanderjs - CLI library

minimist - for arguments parsing

yargs - arguments parsing

And not to mention libraries like chalk that helped us with colors.

Recap

I hope you got a thing or two about building CLI applications with NodeJS.

A common practice I did not mention is that, once your app is working fine, most libraries put the file into a bin folder, and this way, npm knows how to work with executables. This is not a requirement, but regardless of where you place the executable, you should update package.json bin property.

As an excercise, try to add a Delete command to the CLI.

Happy Coding.

via Scotch.io https://ift.tt/2MzHuir

#IFTTT #Feedly

0 notes