FilmUp

filmup

Startups of The Year 2023 Winners: North America 

The Child of the Ages

HackerNoon Reporter: Please tell us briefly about your background. 10-years experience in media industry, 8+ years startup experience, worked with big brands like Google, Facebook, and Huawei. What's your startup called? And in a sentence or two, what does it do? Filmplace. We’re a marketplace that connects brands with unique locations. Just like AirBnB but for the film and media industry. What is the origin story? Filmplace was founded in 2019 to solve a global problem within the industry. Looking for a location for your videos or photos takes 4-7 days, and it cost tons. With Filmplace, you can secure locations within a matter of minutes and cut costs by over 80%! What do you love about your team, and why are you the ones to solve this problem? We are a global team that consists of me (CEO), my CTO (technology), CSO (strategy), CFO (Finance). On top of that, we have the head of partnership, business development, tech, community team. We are young and passionate about what we do and always hungry to strive for more. With this mindset, we can achieve higher and reach for the stars. If you weren’t building your startup, what would you be doing? That’s a good question. I believe many people will answer they will work for some company but for myself, I just couldn’t imagine not building my startup. I always have 101 ideas that may potentially change the world. (Many people who know me will agree) At the moment, how do you measure success? What are your core metrics? Success isn’t measured by numbers and metrics. Everyone has a different idea for success. As for myself, it would be building something that can excite everyone and at the same time, solving big problems globally. What’s most exciting about your traction to date? $0 cost per acquisition, but managed to get big brands that are already using Filmplace such as Tik Tok, Shopee, AirBnB, Microsoft, Dell, Warner Music, etc. What technologies are you currently most excited about, and most worried about? And why? Cybernetics. Can humans really live forever? Or will fully conscious AI take over humans one day? What drew you to get published on HackerNoon? What do you like most about our platform? Curiosity. Makes me feel like I’m in a global blackhat hacking community. (just kidding) What advice would you give to the 21-year-old version of yourself? Please continue to do what I do and never give up. And continue to defer military until you build something first. lol (every Singaporean male needs to serve 2 years) Filmplace was in Startups of the Year hosted by HackerNoon nominated as one of the best startups in Singapore

Lincoln Lin, Filmplace's Founder/CEO, on building the Airbnbs of filming locations

File uploads are a common feature in many web applications, but handling them efficiently and securely can be challenging. In this article, we will explore how to implement efficient file uploads using Node.js, Express.js, and MongoDB. We will cover the entire process, from setting up the server to storing files in MongoDB GridFS, ensuring that your application can handle large files without sacrificing performance. Problem Statement Handling file uploads efficiently involves several challenges: Scalability: Managing large files without overwhelming server memory.
Security: Preventing unauthorized access and ensuring data integrity.
Performance: Uploading and retrieving files quickly.
Storage Management: Efficiently storing and retrieving files from the database. Solution We will use the following stack to address these challenges: Node.js: For the server-side environment.
Express.js: As the web framework.
Multer: Middleware for handling multipart/form-data, which is used for uploading files.
MongoDB: For storing metadata and files.
GridFS: A specification for storing and retrieving large files in MongoDB. Step-by-Step Implementation 1. Setting Up the Project First, let’s create a new Node.js project and install the necessary dependencies. mkdir file-upload-app
cd file-upload-app
npm init -y
npm install express multer mongoose gridfs-stream 2. Creating the Server Next, we will set up a basic Express server. // server.js
const express = require('express');
const mongoose = require('mongoose');
const multer = require('multer');
const { GridFsStorage } = require('multer-gridfs-storage');
const Grid = require('gridfs-stream');
const methodOverride = require('method-override');
const bodyParser = require('body-parser');
const crypto = require('crypto');
const path = require('path');

const app = express();

// Middleware
app.use(bodyParser.json());
app.use(methodOverride('_method'));
app.set('view engine', 'ejs');

// Mongo URI
const mongoURI = 'mongodb://localhost:27017/fileupload';

// Create mongo connection
const conn = mongoose.createConnection(mongoURI, { useNewUrlParser: true, useUnifiedTopology: true });

// Init gfs
let gfs;
conn.once('open', () => {
  // Init stream
  gfs = Grid(conn.db, mongoose.mongo);
  gfs.collection('uploads');
});

// Create storage engine
const storage = new GridFsStorage({
  url: mongoURI,
  file: (req, file) => {
    return new Promise((resolve, reject) => {
      crypto.randomBytes(16, (err, buf) => {
        if (err) {
          return reject(err);
        }
        const filename = buf.toString('hex') + path.extname(file.originalname);
        const fileInfo = {
          filename: filename,
          bucketName: 'uploads'
        };
        resolve(fileInfo);
      });
    });
  }
});
const upload = multer({ storage });

// @route POST /upload
// @desc  Uploads file to DB
app.post('/upload', upload.single('file'), (req, res) => {
  res.json({ file: req.file });
});

// @route GET /files
// @desc  Display all files in JSON
app.get('/files', (req, res) => {
  gfs.files.find().toArray((err, files) => {
    // Check if files
    if (!files || files.length === 0) {
      return res.status(404).json({
        err: 'No files exist'
      });
    }

    // Files exist
    return res.json(files);
  });
});

// @route GET /files/:filename
// @desc  Display single file object
app.get('/files/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }
    return res.json(file);
  });
});

// @route GET /image/:filename
// @desc Display Image
app.get('/image/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }

    // Check if image
    if (file.contentType === 'image/jpeg' || file.contentType === 'image/png') {
      // Read output to browser
      const readstream = gfs.createReadStream(file.filename);
      readstream.pipe(res);
    } else {
      res.status(404).json({
        err: 'Not an image'
      });
    }
  });
});

// @route DELETE /files/:id
// @desc  Delete file
app.delete('/files/:id', (req, res) => {
  gfs.remove({ _id: req.params.id, root: 'uploads' }, (err, gridStore) => {
    if (err) {
      return res.status(404).json({ err: err });
    }
    res.redirect('/');
  });
});

const port = 5000;

app.listen(port, () => console.log(`Server started on port ${port}`)); 3. Testing the Upload Feature We can test our implementation using tools like Postman. Upload a File: Use a POST request to http://localhost:5000/upload with form data containing the file.
Retrieve Files: Use a GET request to http://localhost:5000/files to get the list of all files.
Retrieve a Single File: Use a GET request to http://localhost:5000/files/:filename to get a specific file’s details.
Display Image: Use a GET request to http://localhost:5000/image/:filename to view the image in the browser.
Delete a File: Use a DELETE request to http://localhost:5000/files/:id to delete a file. Conclusion In this article, I demonstrated how to handle file uploads efficiently using Node.js, Express.js, and MongoDB. By leveraging GridFS, we can store and manage large files seamlessly, ensuring scalability, security, and performance. This approach can be further customized and expanded based on specific application requirements, making it a versatile solution for file management in modern web applications. File uploads are a common feature in many web applications, but handling them efficiently and securely can be challenging. In this article, we will explore how to implement efficient file uploads using Node.js, Express.js, and MongoDB. We will cover the entire process, from setting up the server to storing files in MongoDB GridFS, ensuring that your application can handle large files without sacrificing performance. Problem Statement Handling file uploads efficiently involves several challenges: Scalability: Managing large files without overwhelming server memory. Security: Preventing unauthorized access and ensuring data integrity. Performance: Uploading and retrieving files quickly. Storage Management: Efficiently storing and retrieving files from the database. Scalability : Managing large files without overwhelming server memory. Scalability Security : Preventing unauthorized access and ensuring data integrity. Security Performance : Uploading and retrieving files quickly. Performance Storage Management : Efficiently storing and retrieving files from the database. Storage Management Solution We will use the following stack to address these challenges: Node.js: For the server-side environment. Express.js: As the web framework. Multer: Middleware for handling multipart/form-data, which is used for uploading files. MongoDB: For storing metadata and files. GridFS: A specification for storing and retrieving large files in MongoDB. Node.js : For the server-side environment. Node.js Express.js : As the web framework. Express.js Multer : Middleware for handling multipart/form-data , which is used for uploading files. Multer multipart/form-data MongoDB : For storing metadata and files. MongoDB GridFS : A specification for storing and retrieving large files in MongoDB. GridFS Step-by-Step Implementation 1. Setting Up the Project First, let’s create a new Node.js project and install the necessary dependencies. mkdir file-upload-app
cd file-upload-app
npm init -y
npm install express multer mongoose gridfs-stream mkdir file-upload-app
cd file-upload-app
npm init -y
npm install express multer mongoose gridfs-stream 2. Creating the Server Next, we will set up a basic Express server. // server.js
const express = require('express');
const mongoose = require('mongoose');
const multer = require('multer');
const { GridFsStorage } = require('multer-gridfs-storage');
const Grid = require('gridfs-stream');
const methodOverride = require('method-override');
const bodyParser = require('body-parser');
const crypto = require('crypto');
const path = require('path');

const app = express();

// Middleware
app.use(bodyParser.json());
app.use(methodOverride('_method'));
app.set('view engine', 'ejs');

// Mongo URI
const mongoURI = 'mongodb://localhost:27017/fileupload';

// Create mongo connection
const conn = mongoose.createConnection(mongoURI, { useNewUrlParser: true, useUnifiedTopology: true });

// Init gfs
let gfs;
conn.once('open', () => {
  // Init stream
  gfs = Grid(conn.db, mongoose.mongo);
  gfs.collection('uploads');
});

// Create storage engine
const storage = new GridFsStorage({
  url: mongoURI,
  file: (req, file) => {
    return new Promise((resolve, reject) => {
      crypto.randomBytes(16, (err, buf) => {
        if (err) {
          return reject(err);
        }
        const filename = buf.toString('hex') + path.extname(file.originalname);
        const fileInfo = {
          filename: filename,
          bucketName: 'uploads'
        };
        resolve(fileInfo);
      });
    });
  }
});
const upload = multer({ storage });

// @route POST /upload
// @desc  Uploads file to DB
app.post('/upload', upload.single('file'), (req, res) => {
  res.json({ file: req.file });
});

// @route GET /files
// @desc  Display all files in JSON
app.get('/files', (req, res) => {
  gfs.files.find().toArray((err, files) => {
    // Check if files
    if (!files || files.length === 0) {
      return res.status(404).json({
        err: 'No files exist'
      });
    }

    // Files exist
    return res.json(files);
  });
});

// @route GET /files/:filename
// @desc  Display single file object
app.get('/files/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }
    return res.json(file);
  });
});

// @route GET /image/:filename
// @desc Display Image
app.get('/image/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }

    // Check if image
    if (file.contentType === 'image/jpeg' || file.contentType === 'image/png') {
      // Read output to browser
      const readstream = gfs.createReadStream(file.filename);
      readstream.pipe(res);
    } else {
      res.status(404).json({
        err: 'Not an image'
      });
    }
  });
});

// @route DELETE /files/:id
// @desc  Delete file
app.delete('/files/:id', (req, res) => {
  gfs.remove({ _id: req.params.id, root: 'uploads' }, (err, gridStore) => {
    if (err) {
      return res.status(404).json({ err: err });
    }
    res.redirect('/');
  });
});

const port = 5000;

app.listen(port, () => console.log(`Server started on port ${port}`)); // server.js
const express = require('express');
const mongoose = require('mongoose');
const multer = require('multer');
const { GridFsStorage } = require('multer-gridfs-storage');
const Grid = require('gridfs-stream');
const methodOverride = require('method-override');
const bodyParser = require('body-parser');
const crypto = require('crypto');
const path = require('path');

const app = express();

// Middleware
app.use(bodyParser.json());
app.use(methodOverride('_method'));
app.set('view engine', 'ejs');

// Mongo URI
const mongoURI = 'mongodb://localhost:27017/fileupload';

// Create mongo connection
const conn = mongoose.createConnection(mongoURI, { useNewUrlParser: true, useUnifiedTopology: true });

// Init gfs
let gfs;
conn.once('open', () => {
  // Init stream
  gfs = Grid(conn.db, mongoose.mongo);
  gfs.collection('uploads');
});

// Create storage engine
const storage = new GridFsStorage({
  url: mongoURI,
  file: (req, file) => {
    return new Promise((resolve, reject) => {
      crypto.randomBytes(16, (err, buf) => {
        if (err) {
          return reject(err);
        }
        const filename = buf.toString('hex') + path.extname(file.originalname);
        const fileInfo = {
          filename: filename,
          bucketName: 'uploads'
        };
        resolve(fileInfo);
      });
    });
  }
});
const upload = multer({ storage });

// @route POST /upload
// @desc  Uploads file to DB
app.post('/upload', upload.single('file'), (req, res) => {
  res.json({ file: req.file });
});

// @route GET /files
// @desc  Display all files in JSON
app.get('/files', (req, res) => {
  gfs.files.find().toArray((err, files) => {
    // Check if files
    if (!files || files.length === 0) {
      return res.status(404).json({
        err: 'No files exist'
      });
    }

    // Files exist
    return res.json(files);
  });
});

// @route GET /files/:filename
// @desc  Display single file object
app.get('/files/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }
    return res.json(file);
  });
});

// @route GET /image/:filename
// @desc Display Image
app.get('/image/:filename', (req, res) => {
  gfs.files.findOne({ filename: req.params.filename }, (err, file) => {
    if (!file || file.length === 0) {
      return res.status(404).json({
        err: 'No file exists'
      });
    }

    // Check if image
    if (file.contentType === 'image/jpeg' || file.contentType === 'image/png') {
      // Read output to browser
      const readstream = gfs.createReadStream(file.filename);
      readstream.pipe(res);
    } else {
      res.status(404).json({
        err: 'Not an image'
      });
    }
  });
});

// @route DELETE /files/:id
// @desc  Delete file
app.delete('/files/:id', (req, res) => {
  gfs.remove({ _id: req.params.id, root: 'uploads' }, (err, gridStore) => {
    if (err) {
      return res.status(404).json({ err: err });
    }
    res.redirect('/');
  });
});

const port = 5000;

app.listen(port, () => console.log(`Server started on port ${port}`)); 3. Testing the Upload Feature We can test our implementation using tools like Postman. Upload a File: Use a POST request to http://localhost:5000/upload with form data containing the file. Retrieve Files: Use a GET request to http://localhost:5000/files to get the list of all files. Retrieve a Single File: Use a GET request to http://localhost:5000/files/:filename to get a specific file’s details. Display Image: Use a GET request to http://localhost:5000/image/:filename to view the image in the browser. Delete a File: Use a DELETE request to http://localhost:5000/files/:id to delete a file. Upload a File : Use a POST request to http://localhost:5000/upload with form data containing the file. Upload a File http://localhost:5000/upload Retrieve Files : Use a GET request to http://localhost:5000/files to get the list of all files. Retrieve Files http://localhost:5000/files Retrieve a Single File : Use a GET request to http://localhost:5000/files/:filename to get a specific file’s details. Retrieve a Single File http://localhost:5000/files/:filename Display Image : Use a GET request to http://localhost:5000/image/:filename to view the image in the browser. Display Image http://localhost:5000/image/:filename Delete a File : Use a DELETE request to http://localhost:5000/files/:id to delete a file. Delete a File http://localhost:5000/files/:id Conclusion In this article, I demonstrated how to handle file uploads efficiently using Node.js, Express.js, and MongoDB. By leveraging GridFS, we can store and manage large files seamlessly, ensuring scalability, security, and performance. This approach can be further customized and expanded based on specific application requirements, making it a versatile solution for file management in modern web applications.

Efficient File Uploads in Node.js: Using Express, MongoDB, and GridFS for Scalable Storage

Build a Web3 Movie Streaming dApp using NextJs, Tailwind, and Sia Renterd

NextJs, Tailwind, এবং Sia Renterd ব্যবহার করে একটি Web3 মুভি স্ট্রিমিং dApp তৈরি করুন

Erstellen Sie eine Web3-Film-Streaming-dApp mit NextJs, Tailwind und Sia Renterd

Cree una aplicación de transmisión de películas Web3 con NextJs, Tailwind y Sia Renterd

Créez une dApp de streaming de films Web3 à l'aide de NextJs, Tailwind et Sia Renterd

NextJs, Tailwind और Sia Renterd का उपयोग करके Web3 मूवी स्ट्रीमिंग dApp बनाएं

NextJs、Tailwind、Sia Renterd を使用して Web3 映画ストリーミング dApp を構築する

NextJs, Tailwind 및 Sia Renterd를 사용하여 Web3 영화 스트리밍 dApp 구축

Crie um dApp de streaming de filmes Web3 usando NextJs, Tailwind e Sia Renterd

Создание dApp для потоковой передачи фильмов Web3 с использованием NextJs, Tailwind и Sia Renterd

NextJs, Tailwind ve Sia Renterd kullanarak bir Web3 Film Akışı dApp'i oluşturun

Xây dựng ứng dụng phát trực tuyến phim Web3 bằng NextJs, Tailwind và Sia Renterd

使用 NextJs、Tailwind 和 Sia Renterd 构建 Web3 电影流媒体 dApp

How to Build a Chatbot with Langchain, Next.js, OpenAI, and Supabase

Virtual Meetings have become an essential part of corporate collaboration, serving as the de facto way that ideas are exchanged, decisions are made, and strategies are devised. However, the true value of meetings is often diluted by their length and the complexity of the discussions. This is why note-taking and effective summaries and action points are so important. Converting long and often pointless discussions into short (actionable) summaries, meeting attendees can quickly catch up on meetings they missed, review decisions that were made, and understand discussions without having to sift through hours and hours of recordings. We thought it would be cool to create our summarizer. If you don't have one already, keep reading. This technical tutorial will guide you through creating a simple web application that summarizes daily meeting Transcripts using ApyHub’s AI Summarize Document API using NodeJS. Pre-requisites: Access to Google Meet and permission to access meeting transcripts.
A preferred programming language environment (e.g., Python).
ApyHub Account.
GitHub CLI is installed on your computer. Step 1: Clone the GitHub repository Open your terminal and run this command: git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git This command will clone the project in your local environment. Once the project is cloned, you can open the repository in the code editor. Step 2. Install Required Packages: Here, in Node Package Manager (npm), we will install all the dependencies that our application needs to summarize the meeting transcribe. npm install Step 3: Add your API Key to the index.js file. Here, we will add our Secret API key from ApyHub. To generate an API key, you can visit the documentation page of AI Summarize Document API. Your secret looks like this ➡️
apy-token: APY****************************************** Copy this token and paste it in as shown in the code comment below. const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); Once you’ve added the API key. Save the changes using the Ctrl+S Key. Step 4: Running Your Application Once you’ve added the API key. Save the changes using Ctrl+S in your terminal, and run this command.: node index.js That’s it :) As you can see, Now you can generate a meeting transcript anytime you want :) Virtual Meetings have become an essential part of corporate collaboration, serving as the de facto way that ideas are exchanged, decisions are made, and strategies are devised. However, the true value of meetings is often diluted by their length and the complexity of the discussions. This is why note-taking and effective summaries and action points are so important. Converting long and often pointless discussions into short (actionable) summaries, meeting attendees can quickly catch up on meetings they missed, review decisions that were made, and understand discussions without having to sift through hours and hours of recordings. We thought it would be cool to create our summarizer. If you don't have one already, keep reading. This technical tutorial will guide you through creating a simple web application that summarizes daily meeting Transcripts using ApyHub’s AI Summarize Document API using NodeJS. ApyHub’s AI Summarize Document API Pre-requisites: Access to Google Meet and permission to access meeting transcripts. A preferred programming language environment (e.g., Python). ApyHub Account. GitHub CLI is installed on your computer. Access to Google Meet and permission to access meeting transcripts. Google Meet A preferred programming language environment (e.g., Python). ApyHub Account . ApyHub Account GitHub CLI is installed on your computer. Step 1: Clone the GitHub repository Open your terminal and run this command: git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git This command will clone the project in your local environment. Once the project is cloned, you can open the repository in the code editor. Step 2. Install Required Packages: Here, in Node Package Manager (npm), we will install all the dependencies that our application needs to summarize the meeting transcribe. npm install npm install Step 3: Add your API Key to the index.js file. Here, we will add our Secret API key from ApyHub. To generate an API key, you can visit the documentation page of AI Summarize Document API . Your secret looks like this ➡️ apy-token: APY****************************************** AI Summarize Document API apy-token: APY****************************************** Copy this token and paste it in as shown in the code comment below. const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); Once you’ve added the API key. Save the changes using the Ctrl+S Key. Ctrl+S Step 4: Running Your Application Once you’ve added the API key. Save the changes using Ctrl+S in your terminal, and run this command.: node index.js node index.js That’s it :) As you can see, Now you can generate a meeting transcript anytime you want :)

Building an AI-Powered Summarizer using NodeJS and ApyHub API To Make Meetings Easy

240 Stories To Learn About Startups Of The Year

Creating Production Grade Microservices with Go and gRPC

Limited resources, lack of experience in recruiting, and competition with tech giants — hiring talents for an early-stage startup is challenging. The cost of a mistake is sky-high, too: Mishiring might cost of the employee’s first-year salary, which means that a wrong hire for a tech position that pays $60,000 per year, for example, could cost the startup $18,000. That's a great deal of money for a small startup. up to 30% Working as head of recruitment at a VC firm, I know these challenges and help startups avoid financial, time, and reputational losses. Here are five valuable tips for founders to hire well. Focus on attitude — not skills Let's be honest: The startup culture isn't suitable for everybody. Founders should look for individuals with an entrepreneurial mindset and a readiness to work in a hectic environment. Seek out employees who have prior experience running a startup or working for one. If you come across a strong candidate with a corporate background, carefully assess their motivation. Why did they choose to leave a stable job and join a startup? If a candidate who previously worked at a large company is seeking more responsibilities and aiming to advance professionally at a faster pace, then it could be a suitable match. However, when hiring, founders should conduct a thorough job interview. Qualities to look for and interview questions to reveal them Problem-solving. Interview question: Can you describe a specific workplace challenge you've encountered, and how did you go about resolving it? Interview questions: How has your professional life evolved in the last three years? Have you actively sought opportunities to step out of your comfort zone during this time? If so, could you provide an example? What changes /unexpected events affected your work? Could you share a case where you had to adjust to a change you had no control over? Flexibility . Growth mindset. Interview questions: When confronted with an unfamiliar task, how do you approach it? Additionally, how do you stay updated on the latest industry trends and developments? Accountability/Proactiveness. Interview questions: Could you provide a case in which you prevented a problem before it happened? What have you done when you didn’t agree with the solution to the project? Could you provide a case you suggested a solution/idea to your manager and it was successfully implemented? Sense of ownership. Interview questions: Could you share a project or task you've taken a leadership role in? What steps did you take to ensure its success, and how did you demonstrate ownership throughout the process? Goal-oriented mindset. Interview questions: What specific goals did you set for yourself in your previous role? In cases where you couldn't achieve your goals, what actions did you take to address the situation and learn from it? Hiring a senior-level specialist might not be an option given startups' limited resources. Don't chase the "market stars"; focus on promising young talents who will grow with the company. Statistics show that in 2023, almost of early-stage startups are planning to employ juniors, and 27% intend to focus on hiring mid-level specialists. For example, our portfolio startup, All Right, chose this strategy from its very beginning: The founders recruited juniors at an early stage, and now these employees hold leadership positions. 38% Yes, juniors won't bring expertise right away, but they can more easily embrace and adapt to the specific requirements of the startup and take on various roles as the company grows. Juniors require well-organized onboarding, mentorship, and guidance, but they can grow into invaluable assets for a startup later on, assuming more responsibilities and advancing professionally in step with the company's growth. Offer more than just salaries Early-stage startups may not always be able to match the salaries of big brands. What startups can offer is equity or stock options. This can attract candidates who believe in your idea and are motivated by long-term financial gains. (and should) When creating your compensation plan, determine the size of the equity pool. Generally, early-stage startups set aside approximately of their total shares for an equity pool for employees. The number of options granted may be based on the employee’s role, their contribution to the company, and their experience level. 5-15% I know that Filmustage, a seed-stage AI startup, offers 0.5-3% of its total shares to its employees, which can be vested after a year of employment with the company. This way, the company can attract top talent while also aligning employees toward the startup’s success. Avoid overhiring After establishing your startup's immediate objectives, outline the roles and responsibilities required to achieve them. In an early-stage tech startup, key responsibilities might be distributed among three employees: CEO: Guides the company's focus, handles sales, manages early recruiting, and addresses legal issues. CTO: Assumes responsibility for product development, product architecture, and team management. CMO: Focuses on customer acquisition and marketing strategy. In an early-stage startup, this responsibility is often divided among founders. In the very beginning, you can hire a UX designer and a product manager on a part-time basis. As the startup grows, the team may expand to include more tech specialists such as developers and QA engineers. However, there's no need to rush this expansion and attempt to operate like a large corporation — it might not be financially feasible. A common mistake that early-stage startups often make is hiring salespeople as part of their initial 10 hires. At this stage, sales should be led by the CEO. Only after having a product-market fit and understanding sales strategy, you may consider bringing in a dedicated sales manager. Outsource recruiting Founders typically hire the company's first employees using their network. However, once the startup begins to grow, it is often advisable to delegate this responsibility to an outsourced recruiter or seek assistance from your VC . (if you're VC-backed) By outsourcing the recruitment process, founders can concentrate on product development, sales, or marketing, rather than constantly searching for candidates. Additionally, outsourcing recruitment is usually more cost-effective than hiring an in-house recruiter, especially in early hiring. Anastasiia Kuzmenko, Head of Talent Acquisition at . Flyer One Ventures

4 Quick Hiring Tips for Early-stage Startup Founders

Stories, News & Mentions about FILMUP

Filmup’s Stories on HackerNoon