Appbrew empowers brands to build & scale high-conversion mobile apps through a headless no-code platform

Appbrew

appbrew

A step-by-step guide 📙 on how to install, configure and run MySQL 8 server on macOS using Homebrew 🍺 I use Homebrew on macOS to manage all the packages I need for development. Once you understand how Homebrew works and how it helps you manage various packages on macOS, installing any dependency on your Mac becomes easy. We will install Homebrew and learn a few essential commands on how we can use Homebrew. Once through with installing Homebrew, we would then move on to and configure it. install MySQL server using Homebrew What is Homebrew? Homebrew is a package manager for macOS and Linux , but just putting it on record that it works with Linux as well 😊. (I know you would instead use apt-get or yum based on which Linux distro you are using) Why would you use a package manager like Homebrew when all the packages come with their independent files, and these files can be used to install each package independently? We use a package manager because of a couple of advantages package managers have to offer over independently installing each page. .pkg The main difference between Homebrew and the installer package is the fact that Homebrew takes care of the build time dependencies. If the package you are trying to install requires ruby and some of its dependencies, Homebrew does not require you to build/install ruby and libraries from scratch. Homebrew makes the process of installing packages easy. Every installed package is cleanly sandboxed into its cellar (directory), so you don't have stray files all over your system, just symlinks from bin, man, etc. In the case of macOS with Apple Silicon, all the packages are installed in directory. Hence you know where all packages are installed. /opt/homebrew/cellar Homebrew lets you install all the packages with root access and Homebrew installs without root access as well into or /usr/local (Intel) /opt/homebrew (Apple Silicon) Uninstalling is hardly an issue anymore. Homebrew will manage the uninstall process and trim the run time dependencies if needed. Homebrew provides you with many tools to manage all the packages installed on your machine, which includes various commands to list the packages installed, uninstall them, upgrade packages, search for packages, and so on. Step One: Installing the Xcode Command Line Tools Before we install any package or Homebrew itself, we first need to install the Xcode Command Line Tools. To do so on your Mac and run the following command. open the Terminal app xcode-select --install Step Two: Install Homebrew If you do not have Homebrew installed on your machine, you can follow along, but if you have Homebrew installed and already working with it, you can move on to the next step. You can check if Homebrew is installed on your machine by running the following command in your Terminal. brew --version If Homebrew is installed on your Mac, you should get a response containing the version of the Homebrew installed on your machine, which should look like this. Homebrew >=3.x.x

// Where 3.x.x is the version of the Homebrew installed on your machine. 
// Anything above 3 is good If Homebrew is already installed, you can move to the next step. If not, hang on while we install Homebrew. To install Homebrew, run the following command in your Terminal. /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" The above command should install Homebrew for you and add it to the Path. If you are curious about Homebrew's steps while installing your machine, you can . read them here Once Homebrew is installed and rerun the following command to check if Homebrew was installed successfully on your machine. restart the Terminal app brew --version If Homebrew is installed on your Mac, you should get a response that will contain the homebrew version installed on your machine and should look like this. Homebrew >=3.x.x

// Where 3.x.x is the version of the Homebrew installed on your machine. 
// Anything above 3 is good Step Three: Install MySQL 8 Once Homebrew is installed, we will use it to install MySQL 8 on our machine. We would use the to install MySQL on our Mac. Still, run the following command in your Terminal to start the MySQL installation. MySQL formula brew install mysql Step Four: Configure MySQL The above command will install the latest version of MySQL on your Mac. Once MySQL is installed, we need to run the secure installation to assign a password to the root user and create and connect to databases using the root user. You might decide to create another user and not use the root user. But, for this tutorial and assuming that you are installing MySQL on macOS for development workloads, I will stick to using the root user. To secure your MySQL installation, run the following command. mysql_secure_installation Once you run this above command, you will be requested to assign a password to the root user, and you will see the following prompt in your terminal window. You can enter your preferred password for the root user. This will be the password you will use to connect to your database and perform all operations with MySQL. Next, MySQL asks you if you want to enable the . The validate password component helps you ensure that users of MySQL use passwords with minimum strength and characters. Validate Password Component This is super helpful for production loads where many users are using MySQL, and you want to force strong passwords for all the users. Feel free to use it for production environments, but I will skip it for this tutorial because I am assuming you are configuring MySQL for development and not production. So as a response to this question, I will type and press return. At this point, MySQL will ask you whether you want to keep the password you just entered for the root user or you want to set a new password. Since we want to keep the password we already assigned to the root user, type in in your Terminal and press enter. No No By default, MySQL creates anonymous users, and now it will ask you whether you want to remove the anonymous users. We can remove the anonymous users as we don't need them and reply to this prompt with a and press the return key. Yes Then you get a prompt asking whether you want to disable the remote login for the root user. We will go ahead and disable the remote access for the root user, reply to this prompt with a , and press the return key. Yes As the next step, you are asked if you want to remove the test database MySQL created. Reply to this with a as well, which should remove the test database. Yes Finally, you are prompted to reload the privileges table for all the changes to take effect. Reply to this with a and press the return key. Yes With this, we have successfully installed MySQL 8 using Homebrew. Now let's go ahead and create a new database. Step Five: Create a New Database To create a new database with MySQL, we need to sign in as a root user to MySQL in our Terminal. To sign in as a root user, use the following command: mysql -u root -p Once you use this command, you will be prompted to enter your password. Enter the root password you created during the installation process. Once you enter the password, you should be logged into MySQL, and your terminal prompt should now show like so: mysql Once you see the above prompt, you can create a new database using the following command. CREATE DATABASE db_name;
// db_name is the name of your database; name it whatever you want to You should get the following response from MySQL: Query OK, 1 row affected (0.01 sec) That's it; you have a new database that you can use with the as the username and password assigned to the root user. root Subscribe 🙏😊 If I could help you, consider subscribing to , where I keep posting in-depth tutorials, and all stuff is edutainment for software developers. You can also follow me on Hashnode; here is my profile handle @ . Leave a like if you liked the article; it keeps my motivation high 👍. Cloudaffle, my YouTube Channel Cloudaffle Also published . here

How to Install MySQL 8 on macOS Using Homebrew

One of the things that you end up developing in one point or in the other is a breadcrumbs navigation system. I've seen some posts across the web touting how to achieve it in React and Reach Router by providing complex looping mechanisms. In this post, I show you a simpler, non loop way that displays breadcrumbs in Reach-Router. I'll be using CSS-In-JS (Not required), React 16.13 (could be lower), TypeScript, and Reach-Router 1.3.x. No hooks are needed, but components are functional. Here's all the code that you'll need. type BreadrumbsProps = { : string;
    text: string;
    className?: string;
  }; useStyles = makeStyles( ({ : { : ,
    }, : { : ,
    }, : { : ,
    }, : { : ,
    }, : { : ,
    },
  })); AppBreadcrumbs: React.FC<RouteComponentProps> = memo( { styles = useStyles(); ( <Router primary={false}>
          <Bread path="/" url={'/'} text={'Home'} className={styles.left}>
            <Bread
              path={"/evaluation"}
              url={"/evaluation"}
              text={'Evaluation'}
            >
              <Bread
                path="instruments"
                url={'/evaluation/instruments'}
                text={'Instruments'}
              >
                <Bread
                  path=":classId/:period/:instrument/*"
                  url={'../'}
                  text={'Period'}
                ></Bread>
              </Bread>
              <Bread
                path="indicators"
                url={'/evaluation/indicators'}
                text={'Indicators'}
              ></Bread>
            </Bread>
            <Bread
              path={"/planning" + '/*'}
              url={"/planning"}
              text={'Indicators'}
            ></Bread>
            <Bread
              path={"/attendance" + '/*'}
              url={"/attendance"}
              text={'Asistencia'}
            ></Bread>
            <Bread
              path={"/scores" + '/*'}
              url={"/scores"}
              text={'Calificaciones'}
            ></Bread>
            <Bread
              path={"/content" + '/*'}
              url={"/content"}
              text={'Contenido de Clases'}
            ></Bread>
          </Bread>
        </Router> <div className={styles.clear} />
      </>
    );
  });
  
  export default AppBreadcrumbs;
  
  const Bread: React.FC<RouteComponentProps & BreadrumbsProps> = memo((props) => {
    const styles = useStyles();
    const shouldRenderCrumb = !props.location?.pathname.endsWith(
      props.path || '',
    );
    return (
      <div className={props.className}>
        <LinkButton size="small" variant="text" to={props.url}>
          {props.text}
        </LinkButton>
        {shouldRenderCrumb && React.Children.count(props.children) > 0 && (
          <div className={cls(styles.right)}>
            <div className={cls(styles.left, styles.separator)}>{'>'}</div>
  
            <div className={styles.left}>{props.children}</div>
          </div>
        )}
      </div>
    );
  }); url // This is material-ui. You can use any CSS-In-JS approach. const => () root display 'block' right float 'right' left float 'left' clear clear 'both' separator padding '6px' export const ( ) => props const return <> You define all of the crumbs inside the component as if it were normal routes. AppBreadcrumbs Here's an example (Sorry it's in Spanish - It's an actual application that we've been working in) Let's break it down: Reach-Router allows us to have as many Routers as we'd like. By specifying it with we instruct Reach-router not to use the router for main navigation, this allows us to display the inner content of the router. <Router primary={false}> ... </Router> We also need to create an additional component, which we will be calling it because we need to: <Bread/> Format its content. Reach-router creates all of the inner routes as children wrapped in s. We need to do some CSS to make them all float next to each other. <div> Prevent Reach-Router from complaining. Any direct children inside the which doesn't have a path attribute will cause Reach-Router to throw an error. <Router></Router> Designing the <Bread> component Bread: React.FC<RouteComponentProps & BreadrumbsProps> = memo( { styles = useStyles(); shouldRenderCrumb = !props.location?.pathname.endsWith(
      props.path || ,
    ); ( <LinkButton size="small" variant="text" to={props.url}>
          {props.text}
        </LinkButton> <div className={cls(styles.right)}>
            <div className={cls(styles.left, styles.separator)}>{'>'}</div>
  
            <div className={styles.left}>{props.children}</div>
          </div> );
  }); const ( ) => props const const '' return < = > div className {props.className} {shouldRenderCrumb && React.Children.count(props.children) > 0 && ( )} </ > div Its CSS useStyles = makeStyles( ({ : { : ,
    }, : { : ,
    }, : { : ,
    }, : { : ,
    }, : { : ,
    },
  })); const => () root display 'block' right float 'right' left float 'left' clear clear 'both' separator padding '6px' Note that the it's just a component that wraps it in an and tags. <LinkButton> <a> <button> Nothing out of the extraordinary happens here. We overcome the limitation of the children in Reach Router by passing its text as props and rendering it into the component. We also dynamically render the crumb separator or marking (In this case it's just an amersand ) by checking whether it doesn't have more children in it, and if the path is successfully matched. > Clearing div We add a with a css property at the very end to prevent elements from stepping next to it. <div> clear:both Some notes in the route Only use on the route's path if there's no more children, and you'd like for the route to be displayed in all of its descendants (See and .) /* /content /scores Do not add at the end of the route's path if you have children. (see the route) /* /evaluations That's it! Follow me on Instagram, TikTok, Snapchat, Twitter, Facebook @josejaviasilis.

Simple Breadcrumbs in React with Reach-Router [Tutorial]

In this short tutorial I’ll show you how easy it is to add a CMS to a simple browser app using the . It will literally take you 2 minutes to build. Our app will consist of just 3 files: Cosmic JS API 1. index.html2. app.js2. package.json Let’s get started. In your terminal of choice run the following commands: mkdir easy-browser-examplecd easy-browser-examplenpm install cosmicjsnpm install browserify -g Now let’s build our index.html file. Run the following command in your terminal: vim index.html Add the following to our index.html file: <!DOCTYPE html><html><head><title>Cosmic JS Easy Browser Example</title></head><body><h1 id="title">If you see this, something isn't working...</h1><div id="content"></div><div id="metafields"></div><script src="app.browser.js"></script></body></html> We could just as easily use jQuery and Ajax to render our content, but for this example we will use the . official Cosmic JS Node.js package _The official client module for Cosmic JS. This module helps you easily add dynamic content to your website or…_www.npmjs.com cosmicjs Now create a file called app.js: vim app.js And add the following to app.js: // app.jsvar Cosmic = require('cosmicjs')const bucket = { slug: 'easy-browser-example' }const object = { slug: 'home' }Cosmic.getObject({ bucket }, object, (err, res) => {var object = res.objectdocument.getElementById('title').innerHTML = object.titledocument.getElementById('content').innerHTML = object.contentdocument.getElementById('metafields').innerHTML = '<pre>' + JSON.stringify(object.metafields, null, 2) + '</pre>'}) Notice that in our app.js file we are returning content from the , and then attaching our content to the DOM elements at “title”,”content” and “metafields”. Cosmic JS API Next we’ll add a package.json file that will allow us to add some simple scripts to “browserify” our app.js file: vim package.json Add the following to a new file titled package.json: {"name": "easy-browser-example","main": "app.js","scripts": {"browserify": "browserify app.js -o app.browser.js"}} Now let’s run our our scripts to bundle our code into the browser. Run the following script which will bundle the new file to app.browser.js: npm run browserify Now view the index.html file in your browser and you will see that the content from our example bucket “easy-browser-example” can be seen and the metafields data is rendered to a string to show you what data is available. Taking this a step further, you can see how powerful this can be if you add or into the mix. React Angular I hope you enjoyed this short tutorial. If you have not already, you can , and begin playing with this example using content from your own bucket. Cosmic JS offers an intuitive API that can deliver content to any website or application. This gives you the freedom to build your application using any programming language and allows for easier scaling within your development team. Get started by reading . sign up for a Cosmic JS account the documentation This article was written by and originally appeared on the . Tony Spiro Cosmic JS Blog Recommended Reading: _In this tutorial I’m going to show you how to create a simple blog using React, GraphQL and Cosmic JS. This is going to…_hackernoon.com How to Build a Simple Blog Using React and GraphQL

Stories, News & Mentions about APPBREW

Appbrew’s Stories on HackerNoon